Fix EventDocument migration for real now

svthalia · Jun 22, 2023 · cdb32af · cdb32af
1 parent 223e081
commit cdb32af
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 5 deletions.
diff --git a/website/events/admin/__init__.py b/website/events/admin/__init__.py
@@ -1,4 +1,5 @@
 # ruff: noqa: F403
+from .documents import *
 from .event import *
 from .external_event import *
 from .registration import *
diff --git a/website/events/migrations/0068_eventdocument.py b/website/events/migrations/0068_eventdocument.py
@@ -11,12 +11,12 @@ def populate_eventdocument(apps, schema_editor):
         NewEventDocument.objects.create(
             document_ptr=event_document.document_ptr,
             owner=event_document.owner,
-            # For some reason, django INSERTs the existing Document row again (not only
-            # the new EventDocument row), but without the `created` field, as it's not
-            # actually creating a new Document. The DB doesn't allow this, as INSERT
-            # statements must specify all columns, and `created` is not nullable.
-            # So we can manually set created explicitly to solve this.
+            # For some reason we need to copy all fields, because
+            # Django uses an INSERT query on the Document table.
             created=event_document.created,
+            file=event_document.file,
+            members_only=event_document.members_only,
+            name=event_document.name,
         )