On Sep 12, 2:08 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> Well, I use the native version an it works fine. I just wantetd to
> public the error, but if is already known ...
>
> Regards
> Frank
>
> On 11 Sep., 23:09, Joe Wilson <[EMAIL PROTECTED]> wrote:
>
> > This is a known issue.
>
> > The only workaround I can think of is to map the network share to
> > a local drive letter.
>
> >   jdbc:sqlite:t:/some/dir/foo.db
>
> > Side note: SQLite is generally slow on network drives.
> > Also, some network shares suffer from asynchronous writes returning
> > success without writing to the media (so they appear faster), and/or
> > broken POSIX locks. Either could lead to network database corruption
> > if updated by multiple processes simultaneously.
>
> > --- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> > > I experience a problem using the pure java (NestedVM) version of the
> > > SQLite JDBC driver v037. When I try to connect to a UNC drive I get a
> > > "out of memory exception". When I map the same UNC drive to a drive
> > > letter, and try to connect everything is ok. If I use the native JNI
> > > lib (same version v037) it works fine with UNC and with the mapped
> > > drive. Is this a known problem of the NestedVM version?
>
> > > Thanks in advance
> > > Frank
>
> > > java.sql.SQLException: out of memory
> > > at org.sqlite.DB.throwex(DB.java:252)
> > > at org.sqlite.NestedDB.open(NestedDB.java:59)
> > > at org.sqlite.Conn.<init>(Conn.java:60)
> > > at org.sqlite.JDBC.connect(JDBC.java:38)
> > > at java.sql.DriverManager.getConnection(Unknown Source)
> > > at java.sql.DriverManager.getConnection(Unknown Source)
> > > at SQliteUNC.main(SQliteUNC.java:63)
>

I also get this exact error and I'm using Linux.

I'm not sure if there's a distinction between "UNC" and "local" drives
in Linux here.

So I can't use SqliteJDBC/NestedVM at all :-(


--~--~---------~--~----~------------~-------~--~----~
Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en
To unsubscribe, send email to [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---

Reply via email to