Adding "c:" to the start of the file specification worked.  That is a 
change from the old 1.2 behavior?

On Tuesday, June 30, 2015 at 5:53:04 PM UTC-7, Wes Clark wrote:
>
> I'm using the tip of your nightly builds as of about two weeks ago.  I can 
> run in mem mode, but when I try to run in file mode with a URL of either
>
>   
> jdbc:h2:/tmp/guidewire/ferrite/px;AUTO_SERVER=true;MODE=Oracle;CACHE_SIZE=131072;DB_CLOSE_DELAY=-1;LOCK_TIMEOUT=10000
>
> or 
>
>   
> jdbc:h2:file:/tmp/guidewire/ferrite/px;AUTO_SERVER=true;MODE=Oracle;CACHE_SIZE=131072;DB_CLOSE_DELAY=-1;LOCK_TIMEOUT=10000
>
> Did the specification of the location of the a file-mode database change 
> in the last few years.  We've been using an old version for quite a while. 
>  Both of the URLs generate 
>
>   JdbcSQLException: A file path that is implicitly relative to the current 
> working directory is not allowed in the database URL.  Use an absolute 
> path, ~/name, ./name, or the baseDir setting instead.
>

-- 
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.

Reply via email to