Coincidentally (or maybe not) I discovered a hole in the thread
transaction implementation tonight (CAY-446). I am not sure whether
this is related to your problem or not, but it is worth a try with
the fresh code or 02/15 nightly build.
Andrus
On Feb 14, 2006, at 7:00 PM, Andrus Adamchik wrote:
>
> On Feb 14, 2006, at 6:47 PM, Cris Daniluk wrote:
>
>>> There are two "official" ways to avoid commit - external
>>> transactions
>>> and user-managed transactions. Can you explain why commit is
>>> undesirable. Is this a standalone ProcedureQuery, or is this
>>> something you are doing from TransactionDelegate?
>>>
>> Running it from a TransactionDelegate. It is happening after a ton of
>> insert/updates, but before the overall commit. I would be okay
>> with it
>> committing, except that after it commits, the DataContext tries to
>> again and blows up.
>
> That's very strange. Double commit shouldn't happen. Could you post
> the code from the delegate that executes a query?
>
> Andrus
>
This archive was generated by hypermail 2.0.0 : Wed Feb 15 2006 - 00:12:39 EST