Re: [Firebird-devel] Max transaction duration

[Ded <de...@hq...>]

"Ann W. Harrison" wrote:
> Read-only read-committed transactions do not affect the
> OAT - they can go on forever without affecting garbage collection.  In
> this case, unlike the OIT, the transaction must be declared as read-only,
> not just be de-facto read-only.  

  I should remember that since this feature was implemented in FB more
than year ago there were created many applications which used it
starting one common read only read commiting transaction on application
start and closing it on application stop, making changes in short write
transactions. IMHO it's not wise to make this behaviour illegal, so, if
decision to implement transaction-level timeout will be taken, I think
it should'nt be default behaviour but explicitly forced on start of
transaction. But in general I agree with those who said that network and
security problems should be sold on connection level and FB have no need
in transaction level timeouts to serve badly designed applications and
thoughtless usage of interactive tools.

Best regards, Alexander V.Nevsky.