Hmm, you may be better off getting your event listener to store data in
a global data structure, and then creating a stored procedure to query
that data-structure.
Anyhow, that's what I'd do.
Probably more than one way to solve this problem.
On 2012-05-29 16:46, Lizard Lizard wrote:
So I've been digging deeper into event listener, and have accomplished
a bit of what I wanted, in terms of getting it to respond, but now I
have found a fairly amusing problem.
I was told earlier that if I wanted to monitor what event listener was
doing, I could create a memory table. Easy enough. Unfortunately...if
I have an INSERT INTO MYTEMPTABLE type command in SetProgress, it
triggers a listener event which calls SetProgress which... well, you
get the idea.
So I need to create a temporary (memory) table on a DB without a
listener, then have the listener be aware of that DB, and create a
connection to it? Am I missing a much simpler way to do this? I must
be. This just seems like too many hoops, and I must be missing the
forest for the trees, to use a really tiresome cliche.
--
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.
