Hello, I have an application that uses h2 as its database end (embedded). The database contains technical data that will be essential to the running of my application. The amount of this data is massive, in such that it is impractical for end users to install the application and wait for a terribly long time for the application to parse and reconstruct the data from scratch from given files. I last checked it took about 4-5 hours on a fast machine.
I wonder whether it is possible to bundle up the database files for deployment, in such that these files are instantly ready for use by the database upon deployment. My current thinking is to use "jdbc:h2:file:data/test" instead of "jdbc:h2:~/test", and then create "data" directory (under the current directory of the program), and copy the database files there upon installation. Is there any flaw to this approach? Or is there a better approach? The problem is that I will not be there during installation, and I also don't have any control on what kind of machine this application is going to be installed (or even what kind of OS). Any advice? Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
