Hello! If you use an embedded database and your application doesn't use multiple classloaders, your trigger needs to be located in its classpath. If it uses multiple classloaders, make sure H2 and this trigger are loaded by the same classloader. If your tests are loaded separately and other libraries can't see them, you will not be able to load triggers from test cases, you need to move them somewhere else.
If you have a separate H2 server process and your application connects to this server, your triggers should be in classpath of this server. It's possible to specify a trigger as Java code (CREATE TRIGGER … AS 'source code'), in that case H2 will compile it by itself (H2 will need a working Java compiler, JRE is not enough). It isn't related to your question, but please note that H2 1.4.196 is an old unsupported version. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/e5bf2e5b-0b1a-47c8-b66e-893158dc8837n%40googlegroups.com.
