|ask if conversion of database from Derby to MySQL and instalation of this database can be done with tools provided by JChem package|
|My another question concerns academic license - can I use and install MySQL database on local server in my laboratory, so that all users could use it via web-based version of instatnJchem, without installing clients on their computers|
|My another question concerns academic license - can I use and install MySQL database on local server in my laboratory, so that all users could use it via web-based version of instatnJchem, without installing clients on their computers. Of course it would be for local use only.|
Hi Chemaxon team,
I am wondering if one can use the Services/IDE for keeping a local derby database and an Oracle server IJC database in sync?
Would it be possible to make database connections to each?
And retrieve data from the Oracle instance for inserting them into the local derby database via SQL?
I have been experimenting with just this sort of thing as I think there is a very big need for this.
There are potentially a number of possible ways to achieve this, and I have tried a couple:
1. using ETL tools to transfer data from oracle to the derby database
2. using derby's table functions to allow it to connect to tables from other databases (so that you can select data from Oracle directly within Derby)
Both approaches seem to work and can be used to transfer data from Oracle to Derby.
However there is one significant problem. JChem tables are supposed to be managed through the JChem API not directly through SQL. So although I think I have worked out the tricks to make this work it cannot be considered a recommended or supported approach.
If you want more details then let me know. But bear in mind the above warnings.
thanks for the quick answer. I will follow your recommendation (warnings) and avoid syncronization via pure SQL. If burden of manual exporting and importing sd files between server and local database gets to high, the most suitable way to go is probably using the JCHEM API.
Just to clarify, synchronisation of standard tables will not be a problem. Only the JChem tables are of concern as these should be managed through the JChem API not through SQL.
I hope to be able to provide a more complete solution at some stage in the future, as I think this is an important feature for IJC.