I've tried to debug it, but I cannot get significant results; maybe due to
JDK sources not being compiled with -g option (as NetBeans Debugger points
to)

I've done some more testing, with different uri settings, under 168:

*jdbc:h2:~/h2/jplaydb *works perfectly. The folder and database was created
in user.home as expected.

*jdbc:h2:/h2/jplaydb *works perfectly.The folder and database was created
in the root of the hard disk partition, where the application gets launched
from. I don't know if this is the expected behavior, but it works at least.

*jdbc:h2:h2/jplaydb *doesn`t work at all! It should create the folder and
the database under user.dir as in prevoius H2 versions, I guess. No hope!
Here is when I get the connection null.

The above uri works perfectly under 166.

You bet how strange all this sounds to me! ;)

2012/9/19 Thomas Mueller <[email protected]>

> Hi,
>
> There are no error messages at all: the connection returned from the
>> DriverManager is null.
>
>
> Could you debug the DriverManager? That sounds very strange.
>
> 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.
>



-- 
Carlos Hoces
jPlay project <http://www.javaforge.com/project/jplay>

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

Reply via email to