Subject | Re: [ib-support] Deadlocks |
---|---|
Author | Helen Borrie |
Post date | 2001-01-06T10:54:16Z |
At 06:47 PM 05-01-01 -0700, you wrote:
understand the SNAPSHOT isolation level. I was *trying* to indicate to you
places in the documentation where you can find the various isolation levels
and other SET TRANSACTION parameters discussed.
the documentation to get the complete answers on many important
topics. I'm not doing ESQ either but there's stuff in there that isn't
documented anywhere else, that people need to refer to.
isc_tpb_concurrency. It actually doesn't appear in the Index of the API
Guide but you'll turn it up...somewhere else...with reference to the
defaults for the default transaction.
manuals for an unfinished piece of software. The IB manuals have always
been pretty good for including everything but very bad for organisation,
layout and navigation. You really do need to look at ALL the indexes
sometimes.
H.
All for Open and Open for All
InterBase Developer Initiative ยท http://www.interbase2000.org
_______________________________________________________
> > Well, at least we understand why you don't understand.No: you didn't indicate what you had done so far, only that you didn't
> > After you have filled yourself in on the difference between the default
> > transaction (gds_trans) which interbase starts for you if it doesn't get
> > any other instructions...and...an explicit (named) transaction, which you
> > create using SET TRANSACTION, I'm sure you will find a transaction setting
> > that suits what you need to do.
>
>Man I really think we are not talking the same language! I don't understand
>what you mean by named transactions and SET TRANSACTION stuff. I'm calling
>the routine isc_start_transaction to start the transaction and passing in a
>isc_tpb buffer with how the transaction should work (isolation level,
>read-only or read/write, ...). I then pass the ib_tr_handle to the isc_dsql
>routines that need it. Are you saying thats not enough and I need to do an
>isc_dsql_execute of "SET TRANSACTION"?
understand the SNAPSHOT isolation level. I was *trying* to indicate to you
places in the documentation where you can find the various isolation levels
and other SET TRANSACTION parameters discussed.
> > You can set up the default transaction with the parameters you want andUnfortunately, it is the case that you really have to wander around all of
> > actually it's recommended.
> >
> > I guess you have the Embedded SQL Guide there...?
>
>Yes I do though I've not been reading it since I'm not using Embedded SQL.
the documentation to get the complete answers on many important
topics. I'm not doing ESQ either but there's stuff in there that isn't
documented anywhere else, that people need to refer to.
> > >I'm not sure what SNAPSHOT isolation is. Remember I'm using the low levelIt aint easy, I'll give you that. The TPB member you want for SNAPSHOT is
> > >API of isc_* calls. I didn't see anything about SNAPSHOT in the API
> > > manual.
> >
> > Hmmm....are pp. 59 - 72 missing from your API guide?
>
>I have those pages but there is no snapshot isolation method listed. I've
>also looked in the ibase.h include file and its not mentioned there either.
>The manual I have says its the "Interbase 6 API Guide" from Borland and the
>pages you mention are regarding transactions (though 72 isn't the end of the
>chapter). Could I perhaps have an old manual? In the ibase.h file there are
>some isc_tpb things that aren't documented like isc_tpb_ignore_limbo,
>isc_tpb_autocommit, isc_tpb_restart_requests, and isc_tpb_no_auto_undo. Are
>these documented anywhere?
isc_tpb_concurrency. It actually doesn't appear in the Index of the API
Guide but you'll turn it up...somewhere else...with reference to the
defaults for the default transaction.
>I'm fairly confused now both about whether we know what the other is talkingI think none of the above. We are all depending on an unfinished set of
>about, whether I have old manuals, or if I'm completely clueless! Off to do
>the example program which will hopefully clarify exactly what I'm doing.
manuals for an unfinished piece of software. The IB manuals have always
been pretty good for including everything but very bad for organisation,
layout and navigation. You really do need to look at ALL the indexes
sometimes.
H.
All for Open and Open for All
InterBase Developer Initiative ยท http://www.interbase2000.org
_______________________________________________________