I think that is an unfortunate change - it breaks practically all existing relative URL paths in my case because none of them includes that "./" part and it violates the specification of what a relative URL can be which nowhere excludes URLs without the "./" part. Actually, the "./" part is explicitly superfluous and usually a nuisance that one wants to get read of when normalizing URLs.
In my case it may be a reason not to upgrade to 1.4 because the DB is embedded in a system which does its own URL-handling (part of which is a normalization that removes one or more "./" so there is very little I can do. Is there any chance to make it work with all relative URLs again? I know of no other database or other software which enforces this. Johann On Tuesday, 28 April 2015 19:36:57 UTC+2, Thomas Mueller wrote: > > Hi, > > Many users ran into problems because they used something like > "jdbc:h2:test" and then either didn't find the database file, or created a > second database when running the application in a different directory. > That's why in version 1.4.x, now relative path only work when using ".", as > in "jdb:h2:./test". > > The documentation is wrong. I will update it. > > >> jdbc:h2:file:data/sample >> > > It should be: jdbc:h2:file:./data/sample > > Regards, > Thomas > > -- 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.
