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
|
This thread is a continuation of one of the subjects from http://www.mindscapehq.com/forums/Thread.aspx?ThreadID=4290. The only one unsolved problem in the mentioned thread was the foreign identifier problem. Unfortunately it causes my Undo system to fail. Let me quote the subject: Let's assume we have a parent-child nullable relation. When I delete parent, the child.Parent is set to null, but child.ParentId remains untouched. In the database the changes are made correctly. The trouble begins when I try to restore the previous identifier while performing Undo action. Lightspeed in this case recognizes that restored foreign key is the same as it still has in memory, and doesn't set EntityState to changed nor sets relation. The similar situation occurs for 1_to_1 relations. Would it be possible that Lightspeed cleared these incorrect identifiers after/during i.e. SaveChanges? The example of such situation is included in the NUnit tests attached to the mentioned thread, however foreign key checking is commented out in these tests. If necessary I may prepare another example. |
|
|
|
|
As an addition: I've checked it both in LS3 and LS4. |
|
|
|
|
Is there any chance to get it fixed? |
|
|
|
|
Sorry about the delay. We've had a number of support requests recently which have hoovered up quite a bit of our time. Thanks for the reminder -- we will try to look at this asap. |
|
|
|
|
There will be an update for this in the next nightly build. |
|
|
|
|
It looks like the problem is solved! Thank you. :-) |
|
|
|
