Uploaded image for project: 'Zapped: AcousticBrainz'
  1. Zapped: AcousticBrainz
  2. AB-447

Cannot delete a dataset if it has a snapshot

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Dataset editor
    • None

      IntegrityError: (psycopg2.errors.ForeignKeyViolation) update or delete on table "dataset" violates foreign key constraint "dataset_id_fk_dataset" on table "dataset_snapshot" DETAIL: Key (id)=(cd8ecd20-2fdc-4f5e-ba07-c27a3f0bd060) is still referenced from table "dataset_snapshot".

      The entire reason of having a snapshot was so that we could change the dataset and still know the contents of the dataset at the time that a model was trained. 

      In this case I think that we should allow this field to be nullable. Also ties into AB-397, we need to decide what data we delete when a user deletes their account. If the dataset isn't used anywhere we could delete it, otherwise we should anonymise it.

            Unassigned Unassigned
            alastairp Alastair Porter
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:

                Version Package