MySQL Bugs: #52835: Data too long for column 'xxxx' at row 1

Bug #52835	Data too long for column 'xxxx' at row 1
Submitted:	14 Apr 2010 19:35	Modified:	15 May 2010 5:41
Reporter:	Ruben Ruiz	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	5.1.11	OS:	Windows
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	at row 1, BLOB, C#, Connector/Net, csharp, Data too long for column, max_allowed_packet, sharp, text

Description:
I can't find any good answer to this isuue on various search on google is not information to this trouble. sorry but my poor english...

First have trouble with ( max_allowed_packet ) and solve using:
----------------------------------------------------
set global max_allowed_packet =  10485760
-----------------------------------------------------
10485760 = (1048576)x10  using 10 megabites

I try to store simple text content on text/blob column but says error:

Data too long for column ...

How to repeat:
download example on Connector/Net

http://dev.mysql.com/doc/refman/5.1/en/connector-net-programming-blob.html

looks how to use MEDIUMBLOB type for data... for my problem solve LONGTEXT.

change MEDIUMBLOB to blob and crash it...

Suggested fix:
Using MEDIUMBLOB, LONGBLOB and  MEDIUMTEXT, LONGTEXT data type on database, all works correctly

Code used on C#

Attachment: Form1.cs (text/plain), 2.65 KiB.

Hi Ruben and thanks for your report.

I am sorry but I fail to understand you and here is why:
  o This is a c/NET report. Why is category set to Server/Error Code & Messages? Please correct it to c/NET and state the version of c/NET you use.
  o I do not see the file you use nor do I know how big it is.
  o It is generally a bad idea to store files in database. Store a pointer to file instead.
  o There is a problem with "set [global] max_allowed_packet" with several bugs already reported.
  o You have fresh samples in c/NET directory under MySql.Data\Tests\Source (check BlobTest.cs).

There are numerous reasons why data that appears that will fit into some field can grow beyond it depending on your setup. First thing you should do is to start MySQL server *with* general logging (see manual about --log) and check what actually got to server from your program. After that we can discuss further.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

It depends on your data type. Converting text/mediumtext/longtext to blog will often result in the following error message:

"#1406 - Data too long for column ... "

That happens especially if there is already textual data in the given column.

It may be easier to start with a new table with the correct properties to avoid getting this error.

Regards,
Alexander Norton, Stockholm
https://flowerdeliverysweden.se/