Subject | Re: [ib-support] Deadlocks |
---|---|
Author | Brad Pepers |
Post date | 2001-01-06T07:30:35Z |
On Friday 05 January 2001 23:40, you wrote:
the internal locking that Interbase does so I can think about errors like I'm
getting and understand why they are occuring. This is what Sybase has and
helped me understand how it worked.
options in there. The "SET TRANSACTION" will likely be talking about ODBC
isolation levels and locking but I'm a layer below that.
--
Brad Pepers
brad@...
> At 10:12 AM 05-01-01 -0700, you wrote:No I don't expect to do user level locking but I do want to fully understand
> >One thing I would like is a document explaining how Interbase does
> > locking.
>
> IB doesn't do user-applied locking at all. It has MGA (multi-generational
> architecture) and "locks" are managed internally according to isolation
> level, conflict resolution setting and a couple of other conditions that
> may apply.
the internal locking that Interbase does so I can think about errors like I'm
getting and understand why they are occuring. This is what Sybase has and
helped me understand how it worked.
> There's a description of the process in the LangRef notes for SETI've read the DevGuide Working with Transactions many times and tried all the
> TRANSACTION. There is also quite a lot about it in the DevGuide under
> Working with Transactions.
options in there. The "SET TRANSACTION" will likely be talking about ODBC
isolation levels and locking but I'm a layer below that.
> For a link to a white paper about MGA, seeThis sounds good. I'll try it. Thanks again!
> www.interbase2000.org/ib_reallyuseful.htm.
--
Brad Pepers
brad@...