I think I may have figured out the problem. If I change the URL to contain the drive letter, I am now able to access the database from the web console. This was not necessary in 1.3.175, which lead to some confusion when I tried to use the new console. So changing the URL to the following seems to work for me
jdbc:h2:c:\Progra~2\Inform~1\data\process-engine-db\ProcessEngine;AUTO_SERVER=TRUE;MVCC=TRUE;MV_STORE=FALSE On Thursday, May 7, 2015 at 3:09:37 PM UTC-4, Rich Naylor wrote: > > I am attempting to upgrade H2 from v1.3.175 to v1.4.187 in order to obtain > bug fixes from the 1.3 code base. I do not want to switch to the mvstore > system at this time and was advised to add a switch MV_STORE=FALSE to my > connect string. Everything seems functional so far, except I can no longer > access the database using the H2 web console. I receive the following error > when using the h2-1.4.187.jar > > A file path that is implicitly relative to the current working directory > is not allowed in the database URL > > "jdbc:h2:\Progra~2\Inform~1\data\process-engine-db\ProcessEngine;AUTO_SERVER=TRUE;MVCC=TRUE;MV_STORE=FALSE". > > Use an absolute path, ~/name, ./name, or the baseDir setting instead. > [90011-187] 90011/90011 (Help) > > I am able to create a new database with the console, and it does create a > db_name.mv.db file for the new schema. I have a feeling that the web > console is attempting to append the mvstore (.mv) extension to my JDBC URL > and producing an improper connection string as a result. > > Any suggestions to work around this issue ? > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
