Skip to content
This repository was archived by the owner on Mar 13, 2025. It is now read-only.

Behaviour on deletion #64

Closed
callmekatootie opened this issue Nov 7, 2020 · 2 comments
Closed

Behaviour on deletion #64

callmekatootie opened this issue Nov 7, 2020 · 2 comments

Comments

@callmekatootie
Copy link
Collaborator

callmekatootie commented Nov 7, 2020

When a record is deleted, the behaviour expected is as follows:

Safe to delete

No checks will be carried out here:

  • achievement
  • externalProfile
  • organizationSkillsProvider
  • usersAttribute
  • usersRole
  • usersSkill

These exist as sub documents under the user / organizationn and thus are safe to delete

Dependencies

Check if the model is referenced by other models

  • achievementsProvider (see if any achievement uses it)
  • attributeGroup (see if any attribute uses it)
  • attribute (see if any user attribute uses it)
  • organization (see if any external profile or organization skills provider references it)
  • role (see if any user role references it)
  • skill (see if any user skill uses it)
  • skillsProvider (see if any skill uses it)

If yes, prevent deletion and instruct to delete dependent records first

Cascade

If these records are deleted, ensure that there is a cascade deletion on the child records too

  • user (delete achievement, externalProfile, usersAttribute, usersRole and usersSkill)
  • organization (delete organizationSkillsProvider records)
@callmekatootie
Copy link
Collaborator Author

This is now resolved

@callmekatootie
Copy link
Collaborator Author

Changes were taken up in the pgsql migration

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant