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
|
If I mark a property with "Validate Unique" i'm not seeing any unique indexes in Postgresql am I missing something ? |
|
|
You're not missing anything. Uniqueness is something that isn't yet supported in database synchronisation (in either direction). It's a feature we get asked for a lot though so we're going to try to get round to it soon. |
|
|
Thanks, this feature would give me so much more comfort and ease of mind regarding the integrity of the database persisting my model. |
|
|
Okay, the good news: This feature has now been implemented and will be included in nightly builds dated 4 Mar 2010 and above. When you drag a table from Server Explorer or do an Update From Source, unique constraints will be detected and mapped to uniqueness validations. When you do an Update Database, unique validations will be mapped to unique constraints on the column, if you are adding a new table or adding a new column to an existing table. Now the bad news: First, importing unique constraints from database doesn't work with VistaDB, at least not yet. VistaDB users, please contact us if this feature is important to you. Second, updating the database doesn't work if you're altering the uniqueness of an existing column. (This is because on some databases it's more complicated than just doing an ALTER TABLE statement.) In this case, you'll get a message telling you that the column needs to be made unique/non-unique by hand. As always, please let us know if you run into any issues with this feature. |
|