Subject | Re: [firebird-support] Re: Handling Long Transactions |
---|---|
Author | Nando Dessena |
Post date | 2007-01-18T14:51:07Z |
Michael,
M> We solved this quickly by implementing a timer that after 30 min. of
M> inactivity just closed every open window, closing every open query,
M> committing every running transaction and exiting the program.
Talking about throwing babies... While you are at it, why not turn off
the computer and lock it into a cell as well? ;-)
M> I know that people says that I can just use a disconnected architecture.
M> This is a good idea, but it is not easely implemented. At least not in
M> our firm!
Well, legacy is legacy. It is often not at all practical to radically
change the architecture of a working system. Although there are very
good tools out there.
Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================
M> We solved this quickly by implementing a timer that after 30 min. of
M> inactivity just closed every open window, closing every open query,
M> committing every running transaction and exiting the program.
Talking about throwing babies... While you are at it, why not turn off
the computer and lock it into a cell as well? ;-)
M> I know that people says that I can just use a disconnected architecture.
M> This is a good idea, but it is not easely implemented. At least not in
M> our firm!
Well, legacy is legacy. It is often not at all practical to radically
change the architecture of a working system. Although there are very
good tools out there.
Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================