From f0182c7d51dff902a535633a9ca3ab073acc80b8 Mon Sep 17 00:00:00 2001
From: Oliver Falk <oliver@linux-kernel.at>
Date: Thu, 16 Oct 2025 19:10:37 +0200
Subject: [PATCH] Fix Django test database naming conflict

- Remove explicit TEST.NAME configuration that was causing conflicts
- Let Django use its default test database naming convention
- Prevents 'database already exists' errors in CI
- Django will now create test databases with names like 'test_django_db_with_otel'
---
 config.py | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/config.py b/config.py
index e4416db..8d52644 100644
--- a/config.py
+++ b/config.py
@@ -169,9 +169,10 @@ if "POSTGRES_DB" in os.environ:
         "USER": os.environ["POSTGRES_USER"],
         "PASSWORD": os.environ["POSTGRES_PASSWORD"],
         "HOST": os.environ["POSTGRES_HOST"],
-        "TEST": {
-            "NAME": os.environ["POSTGRES_DB"],
-        },
+        # Let Django use its default test database naming
+        # "TEST": {
+        #     "NAME": os.environ["POSTGRES_DB"],
+        # },
     }
 
 SESSION_SERIALIZER = "django.contrib.sessions.serializers.JSONSerializer"