From 1551fba9ab4e4aae71d4b9bae4e906582c714c1d Mon Sep 17 00:00:00 2001 From: Sean Morley Date: Tue, 27 May 2025 12:43:29 -0400 Subject: [PATCH] Refactor migration to set end_date only if start_date is present; improve data integrity during migration process. --- .../adventures/migrations/0030_set_end_date_equal_start.py | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/backend/server/adventures/migrations/0030_set_end_date_equal_start.py b/backend/server/adventures/migrations/0030_set_end_date_equal_start.py index 531f83c..55d5f93 100644 --- a/backend/server/adventures/migrations/0030_set_end_date_equal_start.py +++ b/backend/server/adventures/migrations/0030_set_end_date_equal_start.py @@ -1,12 +1,11 @@ -# Generated by Django 5.2.1 on 2025-05-27 16:38 - from django.db import migrations def set_end_date_equal_to_start(apps, schema_editor): Visit = apps.get_model('adventures', 'Visit') for visit in Visit.objects.filter(end_date__isnull=True): - visit.end_date = visit.start_date - visit.save() + if visit.start_date: + visit.end_date = visit.start_date + visit.save() class Migration(migrations.Migration):