Hi, Well, there is a relatively simple solution for your problem: a trigger on the SESSIONS table. Currently, if adding a row to the SESSIONS table fails, this is ignored (just logged). But what if the server would reject connections if adding the row fails? In that case you could add a trigger on this table that performs whatever code you like (limit the number of connections per user, only allow some users during the day). You still couldn't add custom authentication, but that's not what you need.
> P.S.: Is it possible to order features on a commercial basis ? Yes. I have only a limited amount of time and can't guarantee a short response time, but maybe other H2 developers have more time? I guess I will still be the gatekeeper about what goes into the main database and what APIs to add if custom code is kept externally. Regards, Thomas -- 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.
