Community
Participate
Working Groups
I unchecked the "Cacade Delete Relationships:" checkbox and pressed the Apply button followed by the OK button. In my model i had an assocation between an Entity and a Datatype. On deletion of the datatype from the explorer the association was also deleted, i.e. a cascade delete although cascade delete preference not checked.
It may be because of this ... // This may be turned off by the user through the General preference // page // if (!BasePlugin.getDefault().getPreferenceStore().getBoolean( // GeneralPreferencePage.P_CASCADEDELETE_RELATIONSHIPS)) // return; Its all commented out.
The preference is defined in the ui plugin..... which might explain how we got in this mess... I presume someone commented out the code I highlighted, because it could not be refrerred to when we split ui and bse?
Might even be me, hoping to come back to it, but it looks like it never happened.
So the plan is to move the "General Tigerstripe" Preferences to the BasePlugin. They will still be edited only thoughthe ui plugin, but should be accessible form the Base code
Following a detailed investigation, the logic for the cascade delete is held in the ui and diagram plugins. I will raise a new bug to have that code moved, and for now will disable the preference setting ( as it does nothing!)
The preference option is no longer there in Tigerstripe so I'm unable to reproduce the issue. Please reopen if this is still an issue.
