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, I've been having a problem with cascading deletes. I am using the soft-delete feature. This issue is coming up when I perform a batch of deletes larger than the batch size. What is happening is the SQL that is spit out has some parameters mixed up. If you look at the source for DeleteCascader.BuildCasadingDeletes you will notice the last parameter is a 'criteria' class. Now, in the bottom part of the funciton an exists clause is being built and a reference of the criteria parameter is being given to that query. Now when the command builder parameterizes the query it will bind that criteria to a parameter in the first batch, but since the same criteria maybe used in a exists in another batch it is still bound incorrectly to a parameter number from the previous batch. All that needs to be done to resolve this is have a clone of criteria passed to the exists clause. I did quick patch job that implemented cloning for all criteria classes, it's attached. Thanks, Kavan P.S. Any traction on the Linq beta? |
|
|
|
|
Hi Kavan, We will look into this right away. Regarding the beta, we'll be contacting everyone that has shown interest in the next day or two. I hope that helps, John-Daniel Trask |
|
|
|
