[
https://issues.apache.org/jira/browse/JS2-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma resolved JS2-838.
---------------------------
Resolution: Duplicate
Vitaly,
You're correct that the MSSQL database support isn't correct yet.
But, your patch isn't the right way to fix that removing the cascade actiions
from those constraints isn't enough: the children rows still need to be removed
somehow, right?
I've reopened JS2-812 for that as it better targets the whole problem.
> scripts for mssql database generation doesn't work
> --------------------------------------------------
>
> Key: JS2-838
> URL: https://issues.apache.org/jira/browse/JS2-838
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Persistence and DAO
> Affects Versions: 2.2
> Environment: MS SQL Server 2005
> Reporter: Vitaly Baranovsky
> Assignee: Ate Douma
> Attachments: patchmssqlschema2.txt
>
>
> When I run script for mssql on MS SQL Server 2005 it doesn't create database.
> For foreign keys that references to same table, ms sql server writes next
> error:
> com.microsoft.sqlserver.jdbc.SQLServerException: Introducing FOREIGN KEY
> constraint 'FK_PAGE_MENU_1' on table 'PAGE_MENU' may cause cycles or multiple
> cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify
> other FOREIGN KEY constraints.
> So, for Ms Sql Server there is need to change ON DELETE CASCADE to ON DELETE
> NO ACTION for all foreign keys that references to same table.
> I have a patch to schemas (to phase2-schema.xml and security-schema.xml). But
> after this changes generated scripts will change ON DELETE type of constraint
> (from CASCADE to NO ACTION) for described types of foreign keys for all
> databases (not only for mssql).
--
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]
