Subject | Re: [ib-support] OIT moving when closing connection |
---|---|
Author | Nando Dessena |
Post date | 2002-06-27T13:49:38Z |
Set,
can only talk about Oracle and MSSQL).
This is not to say it's optimal. Native access is usually even better.
I am always interested in bug reports because I have a bunch of BDE
applications that won't get ported to native systems like IBO for a long
time - if ever.
explicit transactions, and it doesn't support all the transaction
options of IB/FB (just readcommitted and repeatableread, in BDE terms);
these are the only "gotchas" that I know of wrt transactions.
Ciao
--
____
_/\/ando
> >Do you happen to actually have used the BDE against IB in the past andThe BDE works much better with IB/FB than with any other DBMS (well, I
> >got bitten by something like that?
>
> No Nando, I haven't - just heard a lot of negative things about it when run
> against IB/FB. So I assumed the BDE would do stupid things like that -
> after all not allowing the OAT to advance isn't really a bug just not how
> things ought to be done.
can only talk about Oracle and MSSQL).
This is not to say it's optimal. Native access is usually even better.
I am always interested in bug reports because I have a bunch of BDE
applications that won't get ported to native systems like IBO for a long
time - if ever.
> But I have done no research to affirm my statement, and retract itIt will do autocommit on a record by record basis if you don't use
> completely. If the BDE does handle transactions decently, I'm just
> positively surprised. Thanks for correcting me.
explicit transactions, and it doesn't support all the transaction
options of IB/FB (just readcommitted and repeatableread, in BDE terms);
these are the only "gotchas" that I know of wrt transactions.
Ciao
--
____
_/\/ando