MySQL Bugs: #8119: MySqlCommand can't deal with really large CommandStrings

Bug #8119	MySqlCommand can't deal with really large CommandStrings
Submitted:	25 Jan 2005 0:07	Modified:	14 Feb 2005 4:03
Reporter:	Jan-Willem Bats	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / NET	Severity:	S3 (Non-critical)
Version:	.NET 1.0.3	OS:	Windows (XP)
Assigned to:	Reggie Burnett	CPU Architecture:	Any

Description:
I was writing an application that created a database dynamically, that is using a really large "create database ..... create table ..... create table ..... create table ....." string that I wanted to pass to the MySql server using the MySqlCommand.ExecuteNonQuery() function.

It didn't want to work because the strings were too long. I figured this out after a few long hours of debugging. So I had to divide my db-creation statement and my table-creation statements over multiple strings.

Then I wanted to fill my database with dummy date, using a really large string with lots of insertions. Naturally, this also didn't work.

I do think, however, that it is fairly relevant to be able to fill databases with more records than 7, so I would appreciate it a lot if you could rewrite the MySqlCommand class so that it is able to work with really large strings.

Otherwise, I think MySql is extremely cool. Keep up the good work.

Sincerely,

Jay

How to repeat:
Ask me for my large statements and try to execute them from within a C# project.

Suggested fix:
Figure out what goes wrong when using large strings, and do something about it.

By the way... I am using the .NET Connector.

Verirfied using a 300K dump

Thank you for taking the time to report a problem.  Unfortunately
you are not using a current version of the product your reported a
problem with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions,
please change the version on this bug report to the version you
tested and change the status back to "Open".  Again, thank you for
your continued support of MySQL.

Additional info:

I believe this is fixed in 1.0.4

I just discovered that I had not tested 1.0.3 properly for this bug so I can not confirm the bug yet.  I will respond again when I do.

Thank you for taking the time to report a problem.  Unfortunately
you are not using a current version of the product your reported a
problem with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions,
please change the version on this bug report to the version you
tested and change the status back to "Open".  Again, thank you for
your continued support of MySQL.

Additional info:

Using the dump given to me by Jorge, I can't reproduce this using the latest code.  Please try 1.0.4 and see if this is still a problem.

The problem was fixed in 1.0.4.

Great job, guys.

Thank you for taking the time to report a problem.  Unfortunately
you are not using a current version of the product your reported a
problem with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions,
please change the version on this bug report to the version you
tested and change the status back to "Open".  Again, thank you for
your continued support of MySQL.

Additional info:

Thanks for getting back to me on this and for using our product.