Hi, > Maybe with a new command like: * LOAD_EXTENSION some_jar_fullpath*
The bad thing in such approach that each time database created you will need run initialization script like LOAD_EXTENSION some_ext1.jar; LOAD_EXTENSION some_ext2.jar; LOAD_EXTENSION some_ext3.jar; etc... In addition better to have system property in which we will list all the classnames of plugins which should be instantiated and initialized for each new database. By the way. I'm thinking about pluggable table implementations. Like this CREATE TABLE T1 (ID INT, NAME VARCHAR) ENGINE "com.aaa.MegaCoolTableFactory" this class will have factory method which will return org.h2.table.Table instance. Thoughts, suggestions? -- 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.
