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

Behaviour on deletion #64

@callmekatootie

Description

@callmekatootie

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy