Feature #775

On Update Cascading Action

Added by Magoni Bruno about 5 years ago. Updated over 4 years ago.

Status:AcceptedStart date:
Priority:HighDue date:
Assignee:-% Done:

0%

Category:CORE
Target version:Unplanned
Sponsor: Ergonomic impact:
Functional impact:

Description

Having a look of easySDI database structure, quite all constraints have got no action attached to ON UPDATE event!
It is very important to define CASCADE action to such event to guaranty data coherence if technical id have to change (i.e. for data migration, for future easySDI changes in sys tables content, and so on...).

So all relations constraint must be altered (in fact removed and recreated) for ON UPDATE event to attach CASCADE action.

History

#1 Updated by Magoni Bruno about 5 years ago

  • Category set to CORE

#2 Updated by Mérour Xavier about 5 years ago

It's a very good thing to have an even more robut solution and be sure we keep integrity in the whole data model.

+1 for me.

#3 Updated by Magoni Bruno about 5 years ago

  • Assignee set to Steering Committee

#4 Updated by Magoni Bruno about 5 years ago

+1

#5 Updated by Teixeira Jérôme about 5 years ago

+1

#6 Updated by Magoni Bruno almost 5 years ago

  • Status changed from Request For Votes to Accepted
  • Assignee deleted (Steering Committee)

#7 Updated by Magoni Bruno almost 5 years ago

  • Target version set to Unplanned

#8 Updated by Magoni Bruno over 4 years ago

  • Target version deleted (Unplanned)

#9 Updated by Magoni Bruno over 4 years ago

  • Target version set to Unplanned

Also available in: Atom PDF