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 recently came across this bug when I looked at the SQL the designer was generating to create new tables and set foreign keys. I have a one-to-many relationship between my entity 'Document' and 'DistributionHistory'. Document has a composite primary key defined in the designer (7 fields), 'DistributionHistory' has a single field primary key. I have defined a one-to-many relationship and used the properties panel to set the column name for foreign key persistence for each of the 7 primary key fields of 'Document' in 'DistributionHistory'. Yet, the sql generated when I click on 'Update Database..' is creating a field in db table called 'DocumentId' and none of the seven fields I specified in the properties window. And setting the foreign key relationship in the db fails because the 7 columns do not exist. |
|
|
Hi, Is it possible for you to send through an example model which reproduces this behavior (it sounds like you may only need to include the 2 entities you have mentioned above) that we can use to diagnose this further?
|
|