[ http://issues.apache.org/jira/browse/JS2-220?page=all ]
Ate Douma closed JS2-220:
-------------------------
Resolution: Invalid
The schema definition is correct.
The table SECURITY_ROLE is totally unrelated in this example: that stores role
definitions defined in an application web.xml
> security-schema.xml invalid relationship
> ----------------------------------------
>
> Key: JS2-220
> URL: http://issues.apache.org/jira/browse/JS2-220
> Project: Jetspeed 2
> Type: Bug
> Components: SSO
> Versions: 2.0-M1
> Environment: Windows XP, Tomcat 5.0.28 with SQL Server 2000
> Reporter: Cord Thomas
> Priority: Minor
>
> 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?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
