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
|
My Mysql Connector is having troubles staying up to date. If i update my database schema (outside of vs2008/lightspeed) and then try to refresh in the server explorer changes are not being picked up. I have to restart Mysql and then choose "Update from source" in the model changes for changes to be picked up there. For changes to be picked up in the server explorer however i have to both restart mysql and visual studio. I am using Lightspeed 3.1 the nightly build from 6th of june and the latest mysql connector 6.2.3 |
|
|
I should say I installed 6.2.3.0 but reference the 5.2.5.0 version of the dll in the solution (as provided in the providers folder). |
|
|
I've not been able to reproduce this problem. The only thing I can think of is if something is causing caching of the MySQL schema across connections. (We create a new connection to the database every time you do an Update From Source, so it's not that we're caching data internally.) You could try turning off pooling in the designer connection string and see if that helps. (You can still keep pooling turned on in the runtime configuration: the designer and runtime connection strings are completely independent.) Another thing you could do is check server-side caching options. We use the same queries each time we interrogate the MySQL schema, so it's possible over-aggressive caching could cause MySQL to return the same results even though the schema has changed. If you're using MySQL Administrator, check the Performance tab and see if turning down the query cache settings improves matters. |
|
|
Hi Ivan i did all the aformentioned but it still didnt work. Something that caught my attention is that the 5.1.3* series introduced the table_definition_cache http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_table_definition_cache Changing this setting had no effect either though. In a last resort attempt I planned to both upgrade to the latest mysql version 5.1.48 or downgrade to 5.0 to see if it would solve matters. I can happily say that updating to 5.1.48 solved the caching issues, although it might have just been the fact that i reinstalled mysql. Thanks for the help ! |
|