The Schema Schema Editor is the expert tool for managing your IJC database. Most simple operations can be performed without needing to use the Schema Editor, but in some cases it may be easier to use the Schema Editor, and some advanced operations can only be performed using it.
The Schema Editor allows you to manage your current IJC Entities and Fields, as well as to add any existing database artifacts that are not yet known to IJC. In this way it lets you incorporate data from an existing database into IJC.
When an object is created in IJC the database artifact is created and IJC is made aware of this together with any additional data that is needed about the item. What happens if the database artifact has not been created by IJC? In this case IJC will not know about the artifact and will not possess the additional information it needs about it to be able to manage it. This may be the case if you have connected to a database that already has tables in it that were created by other means. The Schema Editor lets you see these artifacts and "promote" them into IJC so that it can manage them. Sometimes when you do this you need to provide the missing information to IJC so that it knows how to handle them.
To show or hide these "foreign" artifacts use the Filter toggle button
in the Schema Editor toolbar.
When you have an artifact that is not yet part of an IJC schema you may be able to promote it into IJC. Click on the "Promote" button in the editor. Alternatively you can click on the appropriate button in the toolbar for the type of item that you want to promote. You will see a wizard that takes you through the promotion process. The information your need to provide is typically a subset of the information you need to provide when you create this sort of item in IJC (the information that cannot be read from the database).
Note: Not all "foreign" artifacts can yet be promoted. This is somewhat dependent on the underlying database type.
Entities can be added and removed from IJC using the Schema Editor.
See the Editing Entities page for more details about creating Entities.
Fields can be added and removed from IJC using the Schema Editor.
See the Editing Fields page for more details about creating Field.
Indexes provide the database with a much faster way to find values in a database column. Situations where adding an index will be benefitial (or not) are listed in the Performance tips tips and tricks page.
Please consult your database administrator if you are not clear about indexes.
To add an index in the Schema Editor:
To remove an index in the Schema Editor:
Relationships define associations between entities. Add a relationship in the Schema Editor
by first adding any Fields that are required to define the Relationship and then clicking
on the 'New relationship' in (
)
in the Schema Editor toolbar.
See the Editing Relationships
page for more details about creating Relationships.
A JChem database needs a Property Table which is needed to store various bits of information about the JChem structure tables. By default a single property table named JCHEMPROPERTIES is created when the IJC schema was originally created, and this is sufficient for most purposes. However it is possible to use a different table name, or to to use multiple property tables. Note: this is not recommended unless you have a specific reason for needing to do so.
To manage JChem property tables do the following:
Important: Do not delete JChem tables directly from the database or the information in the property tables will become inconsistent. Always delete them using IJC which will ensure that the property table is updated appropriately. Property tables can also be managed using other ChemAxon tools such as JChem Manager. However, avoid doing this for databases used by IJC or the information may become inconsistent.
Copyright © 1998-2009 ChemAxon Ltd. All rights reserved.