Hi Guys

First can I say thank you for providing the community with a great
resource.

To business: I experience the same problem with this. I get the
journal files, the same errors, the lot. This is with the native
driver on XP (latest everything. yes, really).

I played around for a while trying to get this working.

I eventually came up with a fix that didn't really make sense to me,
but it worked, so hey!

This is:

(first the context: i'm updating the DB with data from a bean)

code before (failing):
            //.... code....
            prep.setString(10, client.getUser_id());
            //prep.execute();
            //..close stuff

code after (working):
            //.... code....
            prep.setString(10, client.getUser_id());
            conn.setAutoCommit(false);
            prep.execute();
            conn.setAutoCommit(true);
            //..close stuff

So this is almost a verbatim copy of the example code to get SQLite
going from your website, David C.

Looking at the API for the setAutoCommit methods, what I did doesn't
really make sense to me as a fix, but fixed the problem.

I am not greatly experienced at SQL and JDBC however I hope this
helps.

I would love to report this with your procedure outlined below but
sadly don't have the time right now.



On Mar 17, 5:46 am, Derek Battams <[EMAIL PROTECTED]> wrote:
> Using v043 (same results with prior versions).  When using the nested
> driver I'm seeing this exception thrown, when I use the native driver
> I don't get this exception.  What I've noticed is that while using the
> nested driver there will be files hanging around alongside the
> database file, they seem to be some kind of journal files.  When these
> files exist I tend to see this exception being thrown.  What I'm
> seeing is this:
>
> 2008-03-16  15:03         7,000,064 sjq.sqlite
> 2008-03-16  15:03                 0 sjq.sqlite-stmtjrnl
>
> Sometimes another file will also exist called sjq.sqlite-journal.  If
> these files are around (0 byte or not) then I seem to get this
> exception being thrown.  When I restart my app I get this exception
> right away, killing the app.  I have to remove these journal files
> then the app starts up again until I do the operation that causes the
> exception again (which is doing a select from a table and looping over
> the result set).
>
> With the native driver, I never see these files laying around nor am I
> able to reproduce the exception (which is easily reproducible within
> my app using the nested driver).  Am I doing something wrong or might
> there be an issue in the nested driver where the journal files aren't
> being removed properly and thereby causing this exception?
>
>   - Derek
--~--~---------~--~----~------------~-------~--~----~
Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en
To unsubscribe, send email to [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---

Reply via email to