From c73be6fac50e770e6a845c74c4830c6678a179da Mon Sep 17 00:00:00 2001 From: Stefan Hacker Date: Sun, 12 Apr 2026 13:00:00 +0200 Subject: [PATCH] fix: Startup-Crash - doppelt definierte Calendar.owner-Relation entfernt User.calendars hat bereits backref='owner', mein zusaetzlich hinzugefuegtes Calendar.owner kollidierte damit und SQLAlchemy weigerte sich, die Mappers zu initialisieren ("Error creating backref 'owner'..."). Damit waren alle Auth-Endpoints tot. Jetzt nur noch Kommentar, die backref uebernimmt die Aufgabe. Co-Authored-By: Claude Opus 4.6 (1M context) --- backend/app/models/calendar.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backend/app/models/calendar.py b/backend/app/models/calendar.py index 05c000a..fefb946 100644 --- a/backend/app/models/calendar.py +++ b/backend/app/models/calendar.py @@ -21,7 +21,7 @@ class Calendar(db.Model): cascade='all, delete-orphan') shares = db.relationship('CalendarShare', backref='calendar', lazy='dynamic', cascade='all, delete-orphan') - owner = db.relationship('User', foreign_keys=[owner_id]) + # Note: `owner` is auto-created as a backref by User.calendars relationship def to_dict(self): return {