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
|
Guys, I have a Table A with an Id and some properties and table B with an Id and some properties, and they have a many to many relationship with table AB with contains table A.Id and table B.Id. LightSpeed seems to demand that table AB has a Id column on it. Is there any way to avoid this? Josh |
|
|
No, there's no way to avoid this. A LightSpeed "through association" depends on the "real" entities having associations to the "through" object, and associations always have to be between entities. Therefore, the "through" object has to be an entity, and therefore has to have an Id. Just a constraint of the implementation I'm afraid. |
|
|
that's not good :-( |
|