This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Please read this post if you are using a LightSpeed nightly build with MySQL and stored procedures. Future nightly builds will update the build of MySql.Data to 5.2.5. This build checks for the existence of stored procedures in a different way to the previously shipped version of MySql.Data. It appears to perform a case-sensitive check for the existence of stored procedures, which did not previously happen. Consequently, if the database name is differently cased in the database and in the connection string, 5.2.5 will fail to find your stored procedures and will throw an exception claiming that they do not exist. For example, if your database name is Sales, but your connection string says "...Database=sales...", you will run into this problem. Therefore, if you are using MySQL stored procedures with LightSpeed, and you upgrade to a nightly build dated 21 Mar 2009 or later, please ensure that your casing is the same across your database and your connection string. This issue does NOT affect the use of tables or views. We apologise for any inconvenience but this is a MySQL behaviour and is therefore outside our control -- sorry! |
|
|
|
