[JS2-220] security-schema.xml invalid relationship

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Invalid
• Affects Version/s: 2.0-M1
• Component/s: SSO
• Environment: Windows XP, Tomcat 5.0.28 with SQL Server 2000
• Assignee: Unassigned
• Reporter: Cord Thomas
• Created: 15/Mar/05 04:49
• Updated: 14/Apr/06 01:01
• Resolved: 14/Apr/06 01:01

Description

In trying to build the db schema for SQL Server 2000, i get an issue related to cyclical cascading delete problems. I wonder whether the security-schema.xml file is valid. There are 3 (or 4?) instances where i believe the foreign key is referring to an invalid table - one such case is:

<table name="SECURITY_GROUP_ROLE">
<column name="GROUP_ID" primaryKey="true" required="true" type="INTEGER"/>
<column name="ROLE_ID" primaryKey="true" required="true" type="INTEGER"/>
<foreign-key foreignTable="SECURITY_PRINCIPAL" onDelete="cascade">
<reference foreign="PRINCIPAL_ID" local="GROUP_ID"/>
</foreign-key>
<foreign-key foreignTable="SECURITY_PRINCIPAL" onDelete="cascade">
<reference foreign="PRINCIPAL_ID" local="ROLE_ID"/>
</foreign-key>
</table>

Shouldn't the second foreign key refer to table SECURITY_ROLE with foreign reference ID?

Is there a database schema diagram somewhere to check for these relationships?