I don't think the transaction table is much help here. It is a snap
shot, there is nothing to prevent a transaction from appearing
immediately after the select returned. In I believe the VTI copies
the data when building the table, so a new transaction could come
about even before the user was finished "next'ing" through the result
set.
Daniel John Debrunner wrote:
Kathey Marsden wrote:
I had asked on the user list if anyone had any ideas about how a user
could conditionally shutdown a database, so that the shutdown would only
occur if there were no active connections to the database. I could not
think of any way for the user to do this so am thinking of possibilities
for a solution on the development side.
My thought is that we could allow a different value for the shutdown
attribute.
shutdown=ifInactive ( or better name)
and for the embedded DataSources, add
setShutdown("ifInactive")
Does this seem like a reasonable enhancement? I haven't researched it
really, but thought I would first see if there were objections.
What's the definition of inactive? No other connections, no other
transactions active? If it was no transactions then wouldn't a select
from the transaction table returning no rows almost fulfill the same
purpose?
I've often thought that a auto-shutdown based upon lack of activity
would be a good thing, it would help to be tied in with auto-matic
checkpointing/data flushing, maybe along the lines of what Raymond is
thinking.
Dan.
