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
|
Previously, when you created an auto through association and set the type to GUID, it would still create the through table with an int type. Now that that's fixed, the designer still breaks when using through associations with GUIDs. What happens is that when you select "Update Database...", the designer still thinks the through tables need to be added even when they don't, so it will never result in an "This database is up to date" dialog. Attempts to re-add the same table will obviously fail. Also, attempts to create new migrations will always find the through tables as part of the next set of changes. The end result is every database change requires me to check off all through tables in both update operations and migration results, which costs a lot of unnecessary time. |
|
|
I've tried to reproduce this but I get the "selected entities are up to date" message and it does not attempt to recreate the through table. I have tried this with both pluralised and non-pluralised table names, and on databases with a GUID type and without a GUID type. Do you have a .lsmodel file you could send us that reproduces the problem? Ideally also the CREATE TABLE statements for the relevant table(s) so we can see the current state what we created in the database. Thanks! |
|
|
Where should I send this info? This is a bit sensitive (sending our app data model), we may also need a mutual NDA for that :( |
|
|
You can send it to ivan @ the obvious domain name. If sensitivity is a concern, try stripping back the model to the minimum set of entities required for a repro. (This would also facilitate our investigation.) You can also rename your entities provided the problem still repros after doing so. This will probably be quicker and cheaper than getting the lawyers involved! |
|
|
Hi Ivan, I think I have a reproducible pattern that doesn't require any private info. Basically the problem occurs when you hav *two* auto-through associations from one table to another, that have different names, when the ID is a GUID. 1) Create an Entity called 'Product' 2) Create an Entity called 'Media' 3) Create a through association for ProductMedia (auto-through from Product to Media tables with GUID) 4) Create a through association for ProductImages (auto-through from Product to Media tables with GUID) Now, the perpetual update reminder will occur on updates and migrations. If you then click "Convert to Explicit Through Table" for both, the problem goes away. Switch back to auto and the problem reoccurs.
|
|
|
Aha! The problem occurs because your through entity name ends in "Media". Because LightSpeed wants expects entity names to be singular, it expects the matching entity in the model to end with "Medium." This case had been handled for normal entities but not for auto through entities. A fix will be included in the 16 July nightly. Thanks for your help in reproducing this, and please let us know if it doesn't fix the problem in your real model. |
|