On Tue, May 29, 2012 at 11:27 AM, Noel Grandin <[email protected]> wrote: > 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. >
Oh, there's usually a thousand ways to solve most problems. I just tend to think of the worst ones first, so, I'm looking to see if anyone else has solved them. I'll look into your idea. What I want to avoid is excessive disk access or DB bloat. I am often working with databases 50+ GB in size (yes, that's a "G", not an "M") so I want the less disk access I can get away with. (This is why having a progress meter during long processes, like uploading or indexing, is so important to me; it's hard to tell "frozen" from "slow" when the processes are expected to take a day or more to complete.) -- ======================= Personal Blog: http://www.xanga.com/lizard_sf Facebook: http://www.facebook.com/lizard_sf MrLizard: Gaming and Geekery: http://www.mrlizard.com -- 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.
