MySQL Bugs: #31518: Using Visual Studio 2005 with MySql Provider

Bug #31518	Using Visual Studio 2005 with MySql Provider
Submitted:	10 Oct 2007 20:25	Modified:	12 Mar 2008 13:30
Reporter:	Willie Johnson	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S1 (Critical)
Version:	5.1.3	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	linux red hat, visual studio 2005, windows xp

Description:
Error happens when i select a table in the server exploror in Visual Studio 2005, i get the error message, "Input string was not in a correct format. Couldn't store <'publish'> in NUMERIC_PRECISION Column. Expected type is Int64. Visual Studio 2005 is installed on a Windows XP Pro OS, and the MySql Database i am trying to access is stored on LINUX RED HAT.

How to repeat:
Add Data Connection in VS Studio 2005 Server Explorer Panel-->Select MySql Provider as the provider-->Click plus sign on Tables to display all the tables-->Click on a Table to expand it, and that when i received the error.

Adding a data source also give the same error when i click Data-->Add New DataSource-->Select All Column or one table-->Click finish.

Suggested fix:
Not Sure

Hi Willie and thanks for your report.

I was unable to repeat the problem with:
 - MySQL server 5.0.50pb running on WinXP Pro SP2 localhost
 - c/NET 5.1 latest snapshot available on http://downloads.mysql.com/snapshots.php
 - VS2005 SP1, no additional properties for connection set (all defaults)

I don't think the location of server matters so if you can provide me with some new info I'll be more than willing to look into this again. Also, please make sure the driver is properly registered in GAC. Does this happen with *every* table or only for specific ones?

Willie, "Access denied for user "the_name_you _gave_me"@my_IP"... Can you check the config and get back to me again? I would like some details on MySQL server used too.

Willie, I will but not before tonight (in about 4 hours). Is that OK?

Maybe it's easier to grant this user a connection from any machine ("%") as my IP will change with each reconnect...

Willie, how about right now (if you're up)?

Willie, I'm in CET and there's 6 hours difference. It's 9:30 here now.

Willie, I respect that situation is sensitive so I'll go with quick-fix first:
 - Set Respect Binary Flags to FALSE

If that doesn't do the trick, set "Use Procedure Bodies" and "Pooling" to FALSE too but I'm convinced first one should do. In any case, 1st table has following fields:
 cat_ID, cat_name, category_...

If you want to solve this problem fully you'll need to allow access for few days more and provide much more info to me, but I think this is not a bug but expected behavior. By additional info I mean:
 - Info on MySQL server
 - my.ini/cnf file used to start server
 - DDL script with some data, suitable for import via mysql cl client

So, what will it be?

Willie, it is not just a connection that I need, please see my other requests. Also, your connection should work now, providing you changed options. I can't be more specific about which options to change until I examine your tables.

Willie, you can cancel that account now, I pretty much have what I need now. Again, I don't think it's a bug. You should check the docs on how c/NET treats fields with BINARY flag set, invalid dates etc and adjust your connect options accordingly.

Willie, do just as you told me (add new or modify existing connection), test the connection and when it succeeds, click Advanced. There you can fine-tune the connection params as I suggested or what seems good to you according to documentation.

Willie, of course you do... You make me "feel" around instead of providing info... I was testing on 5.0.50 while you have 4.1.22 server. Retesting.

Willie, I did some testing on 4.1.22 and I'm pretty convinced 5.1.4GA should be suitable for your use. Can you test with it and get back to me?

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".