search

valvalva / sqlite4java

Automatically exported from code.google.com/p/sqlite4java
0 stars 0 forks source link

job exception #34

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
when I use sqlite4java, I gave a warning 
WARNING: [sqlite] SQLiteBridge$2@15d3388: job exception
com.almworks.sqlite4java.SQLiteException: [1] DB[2] exec() cannot commit - no 
transaction is active at 
com.almworks.sqlite4java.SQLiteConnection.throwResult(SQLiteConnection.java:1192
)  at com.almworks.sqlite4java.SQLiteConnection.exec(SQLiteConnection.java:418) 
at lab.bridge.SQLiteBridge$2.job(SQLiteBridge.java:71)
at com.almworks.sqlite4java.SQLiteJob.execute(SQLiteJob.java:372)
at com.almworks.sqlite4java.SQLiteQueue.executeJob(SQLiteQueue.java:534)
at om.almworks.sqlite4java.SQLiteQueue.queueFunction(SQLiteQueue.java:667)
at com.almworks.sqlite4java.SQLiteQueue.runQueue(SQLiteQueue.java:623)
at com.almworks.sqlite4java.SQLiteQueue.access$000(SQLiteQueue.java:77)
at com.almworks.sqlite4java.SQLiteQueue$1.run(SQLiteQueue.java:205)
at java.lang.Thread.run(Unknown Source)

Original issue reported on code.google.com by warlo...@gmail.com on 18 Aug 2011 at 9:15

Attachments:

GoogleCodeExporter commented 8 years ago 
So, what exactly is the problem? This warning tells you that you're doing 
COMMIT while there's no transaction. It's safe to ignore. You can also check 
SQLiteConnection.isAutoCommit() method, which would return true if there's no 
transaction going.

Does that help or do you think there's a defect in sqlite4java?

Igor

Original comment by ser...@gmail.com on 18 Aug 2011 at 1:18

GoogleCodeExporter commented 8 years ago

Original comment by ser...@gmail.com on 2 Mar 2012 at 4:34