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, I used a "ThroughAssociation" with a "Auto Through Entity" set to "CustomersUsers" (a user may belong to one more customers). When using the "Update Database" command, the designer wants allways to create that table. It was allready created at the first usage of the "Update Database" command. And of course that ends with an error, telling me that the table is allready there. What may cause the problem? I use SQL2005 server, I use the default schema. Kind regards, Sörnt
|
|
|
|
|
Hello Soernt, I've just given this a try and it's behaving correctly for me. Could you provide us a repro case please so we can investigate -- e.g. your .lsmodel file and the CREATE TABLE scripts for your current database schema? Thanks! |
|
|
|
|
Hello Ivan, thank you for looking for my issues! I attached the files. Kind regards, |
|
|
|
|
This occurs because you have given your auto through entity a plural name ("TaskNotificationSubscriptions"). Because this is a CLR class, it ought to have a singular name. It looks like we have an inconsistency where we forgive plural class names for explicit entities, but not for auto through entities, and we'll log this for a fix. But since entity names ought to be singular anyway, we'd recommend that you change the name of the auto through entity to "TaskNotificationSubscription" (without the plural "s"); this will make the problem go away. |
|
|
|
|
Thank you very much! That is working and make sense. Kind regards, |
|
|
|
