We're updating the issue view to help you get more done. 

SQL Server: cascading update/delete on asset_folder/asset object relationship breaks

Description

SQL server throws a Introducing FOREIGN KEY constraint 'fk_a28342a936369207d1d98a1afc86ae07' on table 'psys_asset' may cause cycles or multiple cascade paths. error when trying to setup the FK between asset and asset folder.

I believe that the setup should be that onupdate should be set to cascade unless the DB engine does a cascade cycle check (SQL server):

1 2 // preside/system/preside-objects/asset.cfc property name="asset_folder" .... onupdate="cascade-if-no-cycle-check";

Environment

Status

Assignee

Unassigned

Reporter

Dominic Watson

Accepted

Yes

Fix versions

Priority

Medium