Subject | Re: Next transaction /only/ increments |
---|---|
Author | Smarts Broadcast Systems |
Post date | 2007-11-18T03:25:45Z |
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:
"Autocommit". Usually, this is implemented with COMMIT RETAINING, not
a hard COMMIT. COMMIT RETAINING causes the behaviour you have
described and you are quite right to be concerned about its sins with
regard to garbage collection...
Thanks Helen and Ann. I have filed a bug report with the maintainers
of the DBD::InterBase Perl module. In the meantime, I have a suitable
workaround that keeps the transaction values marching along.
>driver interfaces to default to performing what's sometimes called
> At 06:52 AM 18/11/2007, you wrote:
> >The crux of the question is that ONLY the ``Next transaction'' value
> >increments. All of the other transaction-related counters reported by
> >``gstat -h'' remain static.
> I don't know the DBD::InterBase driver but it's not uncommon for
"Autocommit". Usually, this is implemented with COMMIT RETAINING, not
a hard COMMIT. COMMIT RETAINING causes the behaviour you have
described and you are quite right to be concerned about its sins with
regard to garbage collection...
Thanks Helen and Ann. I have filed a bug report with the maintainers
of the DBD::InterBase Perl module. In the meantime, I have a suitable
workaround that keeps the transaction values marching along.