Uploaded image for project: 'Jetspeed 2'
  1. Jetspeed 2
  2. JS2-1217

Jetspeed Schema Primary Keys and Foreign Key Indexes


    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0, 2.2.1, 2.2.2
    • Fix Version/s: 2.2.2
    • Component/s: None
    • Labels:
    • Environment:
      Jetspeed RDBMS schema


      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.




            • Assignee:
              rwatler Randy Watler
              rwatler Randy Watler
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: