Readonly chemical database

User 6686efeff7

14-02-2013 16:26:02

We are interested in making our chemical databases readonly when, searching. However it appears JChem is trying to write back.  Extract from the HSQLDB log when, running search is given below. Is there a workaround?


 


INSERT INTO JCHEMPROPERTIES_CR VALUES('69c198ffcf2e41d2bf1d7756fce7df9e','2013-02-14 15:55:21.707',0)


COMMIT


DELETE FROM JCHEMPROPERTIES WHERE PROP_NAME='cache.validity_timestamp'


INSERT INTO JCHEMPROPERTIES VALUES('cache.validity_timestamp','2013-02-14 15:55:21.71',NULL)


COMMIT


DISCONNECT


Attaching text file containing stack trace when the database is readonly,


Thanks,


Wiraj

ChemAxon aa7c50abf8

14-02-2013 20:48:29

Hi Wiraj,


You did set this property property to "true": https://www.chemaxon.com/jchem/doc/dev/java/api/chemaxon/jchem/db/DatabaseProperties.html#PROP_READONLY_DATABASE_NAME , correct?


Peter

User 6686efeff7

15-02-2013 14:39:15










pkovacs wrote:

Hi Wiraj,


You did set this property property to "true": https://www.chemaxon.com/jchem/doc/dev/java/api/chemaxon/jchem/db/DatabaseProperties.html#PROP_READONLY_DATABASE_NAME , correct?


Peter



 


It looks like the database needs to be writeable in order to set this property.   


However with this property set, JChem is still trying create a prepared statement,  (this is evident form the HSQLDB stack frames where, the exception originates). The resulting stacktrace is identical to the attachment in my first comment.


Note that when the "PROP_READONLY_DATABASE_NAME"  is set (and the database is writable) the HSQLDB log does not show any writes, therefore it looks like a prepared statement is initialised but not executed.


 

ChemAxon aa7c50abf8

15-02-2013 15:00:49

Indeed. That was what I guessed yesterday while looking into the code of a recent release. This looks like a bug. Which JChem version is this exactly?

User 6686efeff7

15-02-2013 15:26:59










pkovacs wrote:

Indeed. That was what I guessed yesterday while looking into the code of a recent release. This looks like a bug. Which JChem version is this exactly?



5.11.1 

ChemAxon 61b4fee994

21-02-2013 09:03:00

Dear Wiraj,


The fix will be released in version 6.0.


Regards,


Tamas

ChemAxon 61b4fee994

29-05-2013 06:24:09

Dear Wiraj,


The 6.0 version of JChem is released with the fix for this bug.


Regards,


Tamas