Nickolay,

At 04:25 PM 19/09/2003 +0400, you wrote:

>Hello, Roman,
>
> >> This is just an unfortunately the way the driver implements auto
> >> commit mode - I don't know exactly why but it was necessary (at
> >> least as far as anyone could see) to do this to implement
> >> auto-commit with firebird.

Roman wrote"

> > Reason for this is that server supports auto-commit mode using commit
> > retaining (what this is you can read in documentation and ask in
> > Firebird-Support group).
>
> > Unfortunatelly commit retaining might inhibit garbage collection
>
>GC should never be inhibiteded in READ COMMITTED case. Only TIP
>cleanup may need to be inhibited, but I doubt it for retaining
>transactions as they are marked as committed AFAIR. I may perform a
>closer look on this code if you want.
>
>If what I wrote is wrong

It's wrong and it's not a bug. CommitRetaining retains the cursors from
the preceding transaction open and makes the transaction 'interesting"
until a hard commit occurs.

>then it is a bug and should be threated as
>such. You can post post appropropriate item to Bug Tracker along with
>testcase.

You could get a gazillion "test cases". CommitRetaining is *designed* to
work this way. It was put there by Borl to make client/server datasets
behave like Paradox tables. It's a total crock with MVA. It's astonishing
that JDBC should consider it a good enough thing to include as a spec.

Helen