Database Implementation Notes

Whilst Instant JChem tries to behave the same for all supported databases there are times when the different databases do behave differently. This page summarizes the known differences, and other information specific to the particular databases.

Derby

The current version of Derby used is 10.3.2.1.
Once a database column is added its size, scale and type cannot usually be modified. The only exception is that VARCHAR columns can be increased in size (but not decreased).

MySQL

IJC is tested with MySQL versions 5.x. The 4.x version are expected to work but are not tested.
For transactions and foreign key constraints to work correctly MySQL must use the InnoDB table type. Please ensure your MySQL database supports the InnoDB table type. In versions of IJC prior to 2.3 InnoDB had to be specified as the default table type (e.g. the table type that is used if no table type is specified). Since IJC 2.3 this is not longer essential, but is still recommended. Please consult your database administrator to make these configuration changes.

Oracle

IJC is tested with Oracle 9i, 10g, 11g and the free XE version. Earlier versions are expected to work but are not tested.
Oracle 10g's flashback tables (table names begining with BIN) are ignored by IJC.