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 two related tables, I use LINQ to flatten them to use for reporting. It generally works well, however, today one of my customers complained that rows which they deleted are appearing in the printed reports. I check the database, and the DeletedOn field has a date time. Also, the on screen forms for processing the purchase orders are not showing the deleted row. It is only the printer output that is list it. The LINQ I use is as follows: var ops =
From this I can see no reason why the soft deleted records would show. But if I look in pos, the soft deleted record are there. The SQL produced by this is: SELECT As a note, eagerload is enabled from POHeader, and PODetails. I can see form the first select that the joined table t1, is not excluding the soft deleted rows, but t0 is excluding them? Does anyone have any idea why I am getting the deleted rows? Thanks |
|
|
Hi Mark, This appears to be a bug, would it be possible for you to send through a repro of this and we can investigate this further.
Thanks! Jeremy |
|
|
I will try, but it could be a while. I have about six other bug reports in our software I need to look into urgently. If you can track it down without the repro it would be realy helpfu. Thanks Mark |
|
|
Hi Mark, We have added in some changes to tonights nightly build (20101111) which I believe should address this issue for you. Let us know if this still continues to be an issue.
Thanks! Jeremy |
|
|
Hi Jeremy, I have today finally had a chance to download the latest nightly build. Alas, I regret the problem persists. When I use LINQ to LS, it still selects deleted rows from the child tables. I have created a work around for now, but I hope you can fix this properly. My work around was as decribed below. var ops =
|
|
|
Thanks for the update Mark but I am afraid we will need to get a repro of this to investigate it further - if that is cumbersome, perhaps if you could send through just the associated model which is being used above and some associated sample data and I can have a look at setting up a test case from there.
Jeremy |
|