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
|
Hello, I'm in the process of evaluating whether we can replace EF with LS4. In this case, I'm focussing on migrations. To reproduce the issue I am running into, add the attached model to a Visual Studio 2010 C# Class Library. Configure Migrations to be created in a seperate C# assembly. Create Migration "Version1". Version1 schema seems to be correct. Without doing anything to the model, select to create another migration (call it Version2). Since nothing has changed, I would expect no migrartion to be created. Notice however that the Version2 migration actually tries to create duplicate columns for the PersonName and OrganizationName relationships. You can proceed to create as many migrations (I created three more) as you wish and LS4 will continue to generate duplicate columns. It never seems to detect that Version1 migration created the columns. Thanks, Werner |
|
|
It looks like we had a couple of bugs with single table inheritance derived entity migrations, both of which would produce repeated spurious migrations. I've implemented fixes for these and we now handle your model correctly (at least in our test environment). The fixes will be in the next nightly build, available from about 1200 UTC. Many apologies for the inconvenience, and thanks for letting us know about these issues! |
|
|
Thank you. Works great. |
|