If you are trying to prevent users from exceeding memory resources, your best bet is just to use a connection pool and limit the max number of connections. Note that even if a user issues multiple queries in parallel to the same connection, those queries will execute sequentially server-side.
I still maintain that your existing performance will be terrible compared to what it could be, since you are effectively limited by very slow disk IO, even for very small queries. If you limit the max number of connections, and raise MAX_MEMORY_ROWS to a reasonable number, you will experience a net gain in performance. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/CAFYHVnXte%2BOQMcFj6A1RqKXasXdoDFrHhdDaavry4U4qkSk%2B6g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
