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
|
When syncing with our Oracle database, using the designer the FK and PK names are generated starting with SYS_. When we rename them in the database and then try to sync back to the database, it looks like the columns want to be dropped and readded. What are the overall implications of renaming the keys manually in the database and then syncing? No way to name the keys in the designer? Thanks, Brad |
|
|
|
|
The designer has no way to track the history of actions on the database: all it can do is check what the differences are between the database as it stands and the model as it stands. So it doesn't know that column SYS_NEW_NAME is a rename of SYS_OLD_NAME. All it knows is that the model contains something called SYS_OLD_NAME, but that's no longer there in the database, and that the database contains something called SYS_NEW_NAME, which isn't present in the model. So it will ask to delete SYS_NEW_NAME from the database, and add SYS_OLD_NAME. The solution, as you have identified, is to tell the designer what the key columns are called in the database. (This will be necessary anyway for LightSpeed to do the mapping at runtime.) For foreign keys, you do this on the association (select the arrow) using the Column Name property; for primary keys you do it on the entity using the Identity Column Name property. |
|
|
|
