On 2/14/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
> > This doesn't seem like the most intuitive way to block the auto-
> > commit.
>
> No it doesn't :-) It is intended for a very specific use - when you
> want to process an open cursor manually.
Yeah... I wasn't entirely sure it would even work, but seems to :)
> 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.
Cris
This archive was generated by hypermail 2.0.0 : Tue Feb 14 2006 - 18:47:27 EST