Subject | RE: [firebird-support] Who's guilty? |
---|---|
Author | Helen Borrie |
Post date | 2003-12-02T12:07:07Z |
At 11:23 AM 2/12/2003 +0000, you wrote:
one. It's pretty much off-topic for here, as this isn't a Delphi forum.
But, goodness me, there really isn't a BDE driver that fully supports an
ODS 10 database. The 5.2 version (last-ever) that shipped with Delphi 6
doesn't even cut it. If you are getting similar problems with an IB 5.6
database, it might suggest you are using a really ancient BDE.
using them, but using Post and Commit directly?
transactions. That's just about a Guinness candidate.
/heLen
>The app uses the BDE to connect to the database and do its work.Forced writes is a database setting. Your problem is a client-side
>
>We call TDabase.Commit inside a try except block, the exception handles
>calling Tdatabase.Rollback.
>
>I am not too sure what you mean by autocommit and hard commits.
>
>The databases have forced writes enabled,
one. It's pretty much off-topic for here, as this isn't a Delphi forum.
But, goodness me, there really isn't a BDE driver that fully supports an
ODS 10 database. The 5.2 version (last-ever) that shipped with Delphi 6
doesn't even cut it. If you are getting similar problems with an IB 5.6
database, it might suggest you are using a really ancient BDE.
>and we seem to handleCached updates? Is there a particular reason for this? Have you tried NOT
>ApplyUpdates, CommitUpdates in the Tquery objects, then call a
>Tdatabase.Commit.
using them, but using Post and Commit directly?
>Is there something else we should be doing,What you *do* need to do is find what is trapping a million
transactions. That's just about a Guinness candidate.
>if so please please pleaseI can understand that.
>tell me as my customers are also rather annoyed with having to be taken
>down (they are 24/7 medical operations) to backup and restore....
/heLen