You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(api): correct seeding order to respect foreign key constraints
The database seeding was failing with a foreign key constraint violation because it attempted to seed `sources` before `countries`. The `sources` table has a foreign key dependency on the `countries` table.
This change reorders the operations in `seedGlobalFixtureData`, ensuring that `countries` are seeded before `sources`, which resolves the error.
0 commit comments