Page 1 of 1

Error report for check..

PostPosted: Tue Feb 22, 2011 11:52 am
by TomaszN
Hi,
I'm looking for software, that i could use in (automated) testing of my SQLite database (loaded locally). So far i didn't find anything except DB Sanity - seemed to be a good solution but as I've noticed probably it doesn't support SQLite, at least i get an error:

java.lang.RuntimeException: Error in query: select AttributeEntryId from frm_AttributeEntry where AttributeId = 12
at org.databene.jdbacl.QueryIterator.createSource(QueryIterator.java:57)
at org.databene.jdbacl.QueryIterator.(QueryIterator.java:45)
at org.databene.jdbacl.ArrayResultSetIterator.(ArrayResultSetIterator.java:39)
at org.databene.dbsanity.model.query.DefectQueryCheck.query(DefectQueryCheck.java:63)
at org.databene.dbsanity.model.SanityCheckFile.perform(SanityCheckFile.java:75)
at org.databene.dbsanity.model.SanityCheckFolder.perform(SanityCheckFolder.java:65)
at org.databene.dbsanity.model.SanityCheckFolder.perform(SanityCheckFolder.java:57)
at org.databene.dbsanity.DbSanity.execute(DbSanity.java:249)
at org.databene.dbsanity.DbSanity.main(DbSanity.java:371)
Caused by: java.sql.SQLException: SQLite only supports closing cursors at commit
at org.sqlite.Conn.checkCursor(Conn.java:110)
at org.sqlite.Conn.createStatement(Conn.java:194)
at org.databene.jdbacl.QueryIterator.createSource(QueryIterator.java:51)
... 8 more



I added lib for sqlite, configured.properties file, everything seemed to be ok... Is there any way to force closing cursors?

Re: Error report for check..

PostPosted: Wed Feb 23, 2011 3:16 pm
by Volker Bergmann
Hi TomaszN,

this seems to be a limiting concept of SQLite or the JDBC driver you are using.

I can try to work around it. Are you severely interested in using DB Sanity? Then I would try to get around the limit and provide you with a snapshot release for Beta Testing. Unfortunately I do not yet have experience with SQLite and its JDBC drivers, so I would need to rely on your feedback.

Regards,

Re: Error report for check..

PostPosted: Fri Mar 11, 2011 10:41 am
by TomaszN
Hello Volker,

Sorry I didn't reply - I wasn't at work for a few days. Actually I've solved my problem - I have found another tool to test my database, so I don't want You to bother finding solution. Besides - DBSanity was just a try and as far as I understood - it performs test only by checking if particular reusult of a query is NULL, so I can't describe an expected result (correct me if I'm wrong) - for me it's poor validation. However - thanks for Your response..

Greetings,
Tomasz N.