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
|
Hi Guys, I am using MySQL a lot now, but often do not have control over the default table creation engine. And because LightSpeed does not specify the engine the default is used - alot of the time this is MyISAM which ignore all relationships and causes synchronsiation issues as well. Can we get LightSpeed to have an option for MySQL to specify the engine to use. In my personal case I would be happy for it to be set at the model level and have all DB's created with InnoDB. And this would seem fairly logical since using MyISAM dosn't suport relationships - so MyISAM table could be in a different (linked) model but with a MyISAM engine. Cheers |
|
|
|
|
Your wish is our command! * * conditions apply Starting with the next nightly build, you'll be able to add a "MySQL Roundtripping Policy" to your model. This has an option to specify which engine you want the designer to use when creating MySQL tables -- InnoDB, MyISAM or the database default. To add the policy, go into the LightSpeed Model Explorer (the tree view), right-click the model and choose Add New MySQL Roundtripping Policy. The policy will appear in the Policies folder from where you can edit its settings (well, only the one setting for now). (A MySQL policy will be ignored on non-MySQL databases. This allows you to use the same model with different database engines, without having to keep adding and removing roundtripping policies.) Two caveats, one minor, one major: 1. The policy is used only when creating new tables. The designer doesn't check whether existing tables use the specified engine. 2. This DOESN'T currently work with migrations. Migrations will always use the default engine. Let us know if you need migrations support and we'll try to make some time to add it. As always, please let us know whether you run into any bugs or problems. |
|
|
|
|
I'd say migrations support is going to be needed sooner or later so you might as well start planning for it asap :) |
|
|
|
|
Thanks Ivan - Fantastic stuff - I will try this out tomorrow. Cheers |
|
|
|
