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
|
I have a problem with unique constraints during migrations. A model with unique constraints is correctly carried out, if using "Update Database" in the model editor. If we create migrations the constraint is not added to the database. I looked at the migrations code and did not find any hint of a unique constraint. Therefore I guess that there is a problem with the creation of new migrations. I have build a small test project with only one entity and one additional column type string(30) and "Validate Unique" set to true. If you like I can send it to you. I am currently using nightly builds from a few weeks ago and also installed the most recent nightly from 20th december. |
|
|
|
|
Unique validations are currently supported only when adding a new column. I have now added support for adding unique constraints when creating a new table or altering an existing column, and it will be in the next nightly build. Please note, however, that LightSpeed can currently only *add* unique constraints -- it cannot remove them. Other than that, if you still see problems, let us know! |
|
|
|
