Hi, Sorry for the delay. You are right, this is a bug. The auto-server mode can't be combined with an in-memory database, and this invalid combination wasn't detected so far. The next version will throw an exception if you try to open a database in this way.
> %test.db.url=jdbc:h2:play;AUTO_SERVER=TRUE;MODE=MYSQL;LOCK_MODE=0;DB_CLOSE_DELAY=-1 > > then I need to connect to the db using info from the .lock.db file. In > my case the url is > jdbc:h2:tcp:// > 172.20.10.2:49434/12ff45a8d5228ea09fa5b848476c84f20625b0e01fc If you use the full file path in the URL, this is not required: jdbc:h2:/path/to/database/play;AUTO_SERVER=TRUE;MODE=MYSQL;LOCK_MODE=0;DB_CLOSE_DELAY=-1 > Though now I can connect to the play db now but DBVisualizer is > complaining about the missing 'public' schema when i select the > tables. I guess the problem is lowercase identifiers in the DatabaseMetaData methods when using the MySQL mode. This is a known problem which I hope I can soon fix. The workaround is to either not use the MODE=MySQL when using DbVisualizer, or use the MySQL mode in DbVisualizer as you did. 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.
