Re: [Firebird-devel] Max transaction duration

[Christian P. <c_p...@ya...>]

Hi Ann!

> I guess that would depend on the units used.  If you
> can set the
> number of months that a transaction can be open,
> that seems OK.
> If the units are hours or minutes, the chance of
> killing a major
> report or year-end process is high enough to scare
> me off.

I've a customer who have 50 concurrent users and made about 100000
transaction a day over one GDB, this week I was testing a new application
over the same database and today I see this in the static's:

        Oldest transaction    1481648
        Oldest active            1481649
        Oldest snapshot       1481649
        Next transaction       1598010

this is not good, of course, the design of the application is horrible!!!!.
:))

I'm thinking in minutes or hours, but if you don't want to use this feature
you can set it to 0 so the transaction will never be closed by the server.
I think that a feature like this will be a very usefull for critical systems
with hight number of users and for tunning new applications.

Christian