On Sun, Jun 20, 2010 at 3:29 PM, Thomas Mueller < [email protected]> wrote:
> > > Is this different than the SESSIONS table in the INFORMATION_SCHEMA of > the > > TCP connected database? > > > Yes. This table is in the PUBLIC schema. You can add triggers. But > what you want to do (at least it sounds like that's the case) is just > call SELECT * FROM SESSIONS. > I am running with 1.2.37 and the SESSIONS table is in the INFORMATION_SCHEME of the connected database. Am I looking at incorrect data? > > I would not know what connection was broken, just that *a* connection was > > broken. I need to know what connection was broken so I can remove records > > from a memory database that may pertain the that connection. > > Connections don't have a "good" unique identifier except toString(). > How could you find out which one? Maybe using a debugger. > So the Session ID from the SESSION table is part of the toString()? > > > I was thinking that maybe the DatabaseEventListener could have a > > connectionStarted(<Session ID>) and connectionStopped(<Session ID>). > > I will add a feature request for > "DatabaseEventListener.openConnection(id) and closeConnection(id)." > However I will not have time to implement that currently. > If you can give a bit of guidance to where this would go, I will be more than happy to implement and return patches. Jeffrey -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
