[
https://issues.apache.org/jira/browse/JS2-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randy Watler resolved JS2-1217.
-------------------------------
Resolution: Fixed
> 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.0, 2.2.1, 2.2.2
> Environment: Jetspeed RDBMS schema
> Reporter: Randy Watler
> Assignee: Randy Watler
> Fix For: 2.2.2
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
