results table(s) in hsqldb

By default does JChem create them as MEMORY or CACHED tables and is this configurable?





THanks,





-- O.L.

Hi,





JChem creates all HSQLDB tables as CACHED tables.


It is not configurable.





Best regards,





Szilard

That is unfortunate because, if I understand this correctly, it restricts your deployment options: specifically it does not seem possible to package a program that creates CACHED tables as a readonly db since HSQLDB will want to write these tables to disk.





I couldn't be very hard to make this a user-settable parameter...





Regards,





-- O.L.

If I understand you well, want to hold the result tables in the memory.


("read-only" usually means "unchangeable", but I think you do not want that)





Please see my reply in the other topic for an easy solution for this:





http://www.chemaxon.com/forum/viewpost4418.html#4418





Kind regards,





Szilard

> If I understand you well, want to hold the result tables in the memory.


> ("read-only" usually means "unchangeable", but I think you do not want


> that)





I wanted to have the properties and the two structure tables readonly and the result table(s) writable but volatile (i.e., MEMORY, in hsqldb parlance). They don't contain enough query context to be useful across sessions, so there is no reason to persist them. My reading of the HSQLDB manuals is that writable but volatile tables are compatible with persistent read-only table if you use the file_readonly=yes property.





-- O.L.

In nay case I just realize this won't work because you make changes to JCHEM_STRUCTURES_UL when running searches: for this reason alone the db cannot be read-only. What is that table exactly and would it do any harm to edit the HSQLDB script file to make it a memory and hence a volatile table?





-- O.L.

Hi,

Quote:

In nay case I just realize this won't work because you make changes to JCHEM_STRUCTURES_UL when running searches

No, we do not.

Quote:

What is that table exactly

Please read the following topic for further information:





http://www.chemaxon.com/forum/ftopic879.html width="90%" cellspacing="0" cellpadding="3" border="0" align="center"> Quote: would it do any harm to edit the HSQLDB script file to make it a memory and hence a volatile table?


If your database is read-only, then it's fine, but there's no reason for this:


it can also be an empty read-only table in this case.





Regards,





Szilard

Quote:

No, we do not.

I don't think that's correct. When trying to use JChem in readonly mode, I get

Code:

Exception in thread "main" java.sql.SQLException: The database is in read only mode in statement [DELETE FROM JCHEM_STRUCTURES_UL]         at org.hsqldb.jdbc.Util.sqlException(Unknown Source)         at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)         at org.hsqldb.jdbc.jdbcStatement.execute(Unknown Source)         at chemaxon.jchem.db.StructureCache.deleteOldUpdateLogs(StructureCache.java:291)         at chemaxon.jchem.db.StructureCache.load(StructureCache.java:253)         at chemaxon.jchem.db.StructureCache.loadIfNeeded(StructureCache.java:648)         at chemaxon.jchem.db.JChemSearch.loadCacheIfNeeded(JChemSearch.java:2287)         at chemaxon.jchem.db.JChemSearch.search1(JChemSearch.java:2050)         at chemaxon.jchem.db.JChemSearch.search(JChemSearch.java:1897)         at chemaxon.jchem.db.JChemSearch.setRunning(JChemSearch.java:1784)         at chemaxon.jchem.db.JChemSearch.run(JChemSearch.java:1804)         at Test_JChem_1.main(Test_JChem_1.java:18)

Regards,





-- O.L.

You are right, I forgot about this, sorry.





In this case you can create an empty MEMORY table instead, that should work fine.





Best regards,





Szilard

OK. Thanks,





-- O.l.