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
|
Does LightSpeed support virtual foreign keys? A virtual foreign key defines relationship between a table and a view, or 2 views. |
|
|
By support do you mean will we detect these and apply them to the model or is this something you want to have reflected in your model where there isnt an underlying database constraint to match this.
|
|
|
By support, I mean LS designer provides a way to add/edit/delete a virtual (logical) foreign key between 2 entities. The key is persisted in the model, not in the physical database. But it is treated the same way as a real (physical) foreign key, so that navigation fields are generated between the 2 entities. |
|
|
Yes somewhat. You can achieve this by defining a relationship between the 2 entities and then ignoring the relationship when synchronising. This will have the relationship defined in the model but not reflected in the database. The downside with this is you have to keep ignoring that relationship if using the database -> model sync since this expects you are aiming to keep the 2 in sync (which you are not intending).
|
|