Feature Parade for Instant JChem 5.3.4

This page describes new features in IJC 5.3.4 See here for a description of other versions.

• Support for multiple database schemas for Oracle
• List management can use fields other than the ID field
• Delete database artifacts behaviour changed
• Roles required for regenerating JChem tables changed
• Faster startup performance
• Better estimate of Markush library size
• Command-line option to turn off initial data retrieval

Support for multiple database schemas for Oracle

User guide

Previously IJC could only use tables that were in the default schema. In this version we have enabled IJC to access tables and other artifacts from additional database schemas. This allows data from multiple schemas to be viewed together in IJC (e.g. within a single form) and allows better control of security and previleges. The expected use is to provide read-only access to data from additional schemas, but read-write access, and even the ability to create tables is also possible if sufficient privileges have been granted to the IJC Oracle user.

List management can use fields other than the ID field

User guide

Previously IJC could only handle lists for the ID field. Whilst this was OK for most purposes, sometimes you might have a more meaningful identifier in a different field. IJC can now handle lists for any integer or text field, now allowing these other lists to be mananged. In addition values of a list from one field can be converted to those for a different field.

Delete database artifacts behaviour changed

Delete database artifacts chckbox is unchecked by default and remembers your last setting to reduce risk of deleting tables in database by mistake. This was done to reduce the risk of deleting database tables or columns by mistake.

Roles required for regenerating JChem tables changed

Regenerating JChem tables now requires ROLE_ADMIN and ROLE_EDIT_SCHEMA whereas previously it needed either of these roles. This makes it easier to restrict who can upgrade JChem tables and reduces the risk of a privileged user from upgrading the JChem database by mistake.

Faster startup performance

Startup performance should be improved, especially for databases with lots of tables. Meta data for the database atrifacts is now read for all artifacts instead of individually (where possible) reducing the number or hits on the database.

Better estimate of Markush library size

Better estimate of library size for large Markush libraries. Estimate is displayed as exponent of 10 rather than 2. e.g. 10^17.

Command-line option to turn off initial data retrieval

The '-J-Dijc.skipInitialDataLoad=true' command-line option was created to allow the initial retrieval of a hit list for all rows to be turned off. This can be useful in situations where you have very large databases, or slow connections to the database. This option also prevents the determination of the row count of each table as this can also be a slow operation. The row count is displayed as ??? instead of the actual value.
Note: both these features are going to be improved and made more configurable in IJC 5.4.
See startup options for details of how to use this.