Thanks for your fast answer.

I'm using JDK 1.5.0_12 and have tried running with JRE 1.5.0_12 and
1.6.0_01, same problem exists. I tried to recompile the SQLiteJDBC
driver from the sources but make fails under MinGW because of some
escaped characters in binutils.

Have you compiled a new version of the SQLiteJDBC Nested driver with
those patches applied? Maybe even with JDK 1.5.0? If so, would it be
possible to get that version, please?

On Jun 13, 5:55 pm, Joe Wilson <[EMAIL PROTECTED]> wrote:
> Make sure you're using the latest version of NestedVM with fsync support:
>
>  http://nestedvm.ibex.org/dist/nestedvm-2007-01-12.tgz
>
> --- Joe Wilson <[EMAIL PROTECTED]> wrote:
>
>
>
> > You'll get sqlite database corruption with JDK 1.4.x and prior JVMs on 
> > Windows due to bugs in
> > Java.
>
> > Apply these patches to NestedVM to work around the problems:
>
> >  http://groups.google.com/group/nestedvm/msg/782b491b43eca3f1
> >  http://groups.google.com/group/nestedvm/msg/cb5e2823c37329ac
>
> > For some background, read:
>
> >  http://groups.google.com/group/nestedvm/browse_thread/thread/d37aa65e...
> >  http://groups.google.com/group/nestedvm/browse_thread/thread/220d2b30...
>
> > --- [EMAIL PROTECTED] wrote:
> > > If I run VACUUM with the nested driver the result is a database with
> > > size of 4kB and the database is corrupted beyond use. VACUUM works
> > > correctly with the Native driver but the windows version of the driver
> > > leaks memory like mad.
>
> ____________________________________________________________________________________
> TV dinner still cooling?
> Check out "Tonight's Picks" on Yahoo! TV.http://tv.yahoo.com/


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SQLiteJDBC" 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/sqlitejdbc?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to