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
|
I have a couple of tables in the database (SQL 2005) that are joined by a FK that is nullable. When dragging on to the designer, the relationship was not set as nullable, so I corrected this (it was actually a one-to-one relationship, so I set the "Is Target Nullable " to true after changing to one-to one). Is this by design that it doesn't pick up that the FK was nullable or is it a small bug ? |
|
|
|
|
It's a bug. However, we only see this if we first drag on the table containing the FK column and then, in a separate drag, dragging on the referenced table. If we drag on the referenced table first, or drag both on together, we correctly detect the nullability. Is this what you were doing? Just checking in case we have missed a repro case... |
|
|
|
|
Yup, that's what I was doing, cheers Ivan. |
|
|
|
|
This is a bit tricky to fix where we ought to fix it, so instead I've updated the database sync feature to detect changed association nullability. Not ideal, but at least now an Update From Source will fix it automatically for you. |
|
|
|
