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, When I set the Schema for the entity and select the UPdate Datebase option in the designer the designer creates the table but if you do it again the designer ask is you want to create the table again. Also when a custom type is specified the same thing happens e.g. Add a field with a datatype of Money (Custom Type) and right click Update database the designer thinks that the money field is not created. Kind regards, Johan |
|
|
Which database are you using -- SQL Server? |
|
|
Hi Ivan,
Yes - SQL Server |
|
|
Thanks Johan. Unfortunately I can't reproduce either of these problems -- in each case, I get 'the selected entities are up to date' the second time I do an Update Database. Could you check that the issues still occur with current nightly builds, and if so provide me with a small .lsmodel file that exhibits them? Thanks! |
|
|
Hi Ivan, I've created a repo for the update of the database.
Kind regards, |
|
|
Thanks Johan. The problem appears to occur only when the default schema (dbo) is explicitly specified. Is there any reason you need to specify this schema? Is it that user logins default to a different schema? |
|
|
Hi Ivan, Yes my login defaults to a different schema. |
|
|
There'll be a fix in tonight's nightly build. As always, let us know if you still see the problem. |
|
|
Caveat: there is still an issue if you explicitly specify your login default schema. So if your login default schema is 'wildlife' and you specify a schema of 'dbo' -- i.e. your current situation -- you will be fine. However, if you then change your login default schema to 'dbo', you'll hit the remaining part of the bug, and you'll need to remove the explicit dbo schema from the dbo entities. Similarly, if your login default schema is 'wildlife', and you have an entity with the 'wildlife' schema explicitly specified, that entity will not be synced correctly. Will this be a problem for you? Oh, and I really hope this won't affect you, but the fix does not apply to SQL Server 2000. |
|