I'm looking into applying CpBT into my application. On of the things I'm trying to do is set flushmode to never and only commit through explicit flushes. I encounter the following issue when I try to implement this. Btw: this concerns porting a legacy application.
Certain tables have sequence (order) fields that have a unique index over the sequence fields and the parent ID. When I resequence these, I have to put one record aside temporarily to be able to move the records around correctly. So, I have record A with sequence 1, and record B with sequence 2. When I switch them around, I have to move A to 3, B to 1 and then A to 2. The problem with this is that if I do not do an explicit flush after the first mutation, the sequence gets overwritten by the last mutation. Does anyone have experience with this specific issue (or issues like this) and have a suggestion how I solve this with FlushMode.Never abd CpBT? -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
