Hi, About use cases
1) Database initialization service. It will do something on each database creation (run initialization scripts and so on). This is more powerful and sometimes more convenient replacement for initialization parameter of url ;INIT=... Potentially this can be used also for automated loading jars into new db (if this will be implemented). 2) Functions serivice. It will contain set of functions. But there will be even no need to execute initialization scripts - they will work like builtin H2 functions. This will allow to extend H2 set of builtin functions in easy way - simply put jar with UDFs to classpath. We are talked a lot of time about should we include some functions to H2 or not. So any functions that are usually not needed (for example external data access and so on) should be placed in separate plugins. On H2 site this should be also separate downloads. 3) Tables service. To allow user to create his own table implementation best suited for his needs. This is needed by me for data transfer from one application to my application via odbc with maximum performance. Also I think someone can create table implementations that are faster for some use cases than standard. -- 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.
