Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Developers List" <jetspeed-dev@portals.apache.org>
Message-ID: <7008489.359441285219832957.JavaMail.jira@thor>
Date: Thu, 23 Sep 2010 01:30:32 -0400 (EDT)
From: "Randy Watler (JIRA)" <jetspeed-dev@portals.apache.org>
To: jetspeed-dev@portals.apache.org
Subject: [jira] Commented: (JS2-1217) Jetspeed Schema Primary Keys and
 Foreign Key Indexes
In-Reply-To: <910797.346731285172853696.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JS2-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913907#action_12913907 ] 

Randy Watler commented on JS2-1217:
-----------------------------------

4. Statistics schema cannot support replication since no valid primary keys can be established for these raw logging tables. This is the case since all columns as nullable and timestamps are not unique even when paired with any other columns.

> 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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org