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 guys, Attached is a repro demonstrating two cases I'm having issues with. One works with the EnableCandidateFixes flag set to true, while the other works with it set to false. I can't get both to work. These scenarios seem pretty straightforward and standard - they both only happen when using table per type inheritance. In both cases the order of inserts is wrong - either updating a record referencing a table not yet inserted, or inserting the child table before the parent. Would really appreciate it if you can look into these, as they are blocking our work. Cheers, Mark |
|
|
Thanks for providing the concise repro for this. I have tracked down the issue and added a fix which will apply when you are using EnableCandidateFixes (since this is the behavior we will ultimately be promoting in the future). This will be available for you in tomorrows nightly build (tonight's one has already been built Im afraid!), let us know once you have had a chance to check this against your actual systems and let me know if there are any other issues.
|
|
|
Cheers Jeremy, Much appreciated - will let you know how it goes. Thanks, Mark |
|
|
Thanks, the latest nightly has resolved our issues. |
|