Hi, > 3. No support for packages. Internally all classes live in the existing > "org.h2.dynamic" package used for user-defined classes.
Actually I would use whatever package is defined in the source code. If it's the unnamed package, then that's OK. I know it means users can potentially use org.h2.*, but I don't think that's a problem (it will not affect the rest of the system because a separate classloader is used). Advantage: people can just copy & paste the source code 1:1 without having to worry about the package name. > CREATE TRIGGER TRIG_INS BEFORE INSERT ON TEST FOR EACH ROW CALL "WIBBLE" Currently I think it makes more sense to use the complete class name. Reason: there can be multiple classes in the source code. I'm not sure if both the module name and the class name are required. If possible, I would just use the class name. If possible, I would use only one classloader for all modules. 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.
