portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randy Watler (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Created: (JS2-1217) Jetspeed Schema Primary Keys and Foreign Key Indexes
Date Wed, 22 Sep 2010 16:27:33 GMT
Jetspeed Schema Primary Keys and Foreign Key Indexes

                 Key: JS2-1217
                 URL: https://issues.apache.org/jira/browse/JS2-1217
             Project: Jetspeed 2
          Issue Type: Bug
    Affects Versions: 2.2.2
         Environment: Jetspeed RDBMS schema
            Reporter: Randy Watler
            Assignee: Randy Watler

Cleaning up Jetspeed schema correctness issues:

1. Ensure that all tables have a primary key. This is required for DB replication in Oracle
and is generally considered a best practice.

2. Add indexes for foreign key join columns. This is also considered a best practice, especially
when cascade operations are enabled. If a foreign key join column is not indexed, a full table
scan may be required for delete and/or updates, effectively resulting in a table level lock.
These locks are a common source of deadlock in the DB for concurrent operations.

3. Remove foreign key cascaded definitions for the Registry schema. This is done since this
schema is not in normal form and integrity cannot be enforced universally using foreign key
constraints. Delete and update operation cascades are performed programmatically by OJB. By
removing the odd foreign key definition that were in place, this schema will be defined consistently.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message