fix: modify db seed to ensure extension exists before transaction

[w0244079]

Fixes #1005

I was experiencing the same error as was reported in this issue and have submitted a PR to fix which worked for me.

The underlying issue with the seed script was that the CREATE EXTENSION IF NOT EXISTS "uuid-ossp" statement was being executed multiple times within separate seed functions (seedUsers, seedInvoices, seedCustomers, etc.), even though the extension is a one-time setup for the entire database. PostgreSQL does not allow the same extension to be created multiple times, and executing it within each function could still lead to conflicts when trying to insert the extension multiple times during a single database transaction. This caused the 23505 unique constraint violation error, as PostgreSQL detected the duplicate attempt to install the uuid-ossp extension. The solution was to move the extension creation outside of the transactional logic, ensuring it runs once before any other operations and preventing redundant attempts to create the extension.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
next-learn-starter	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 26, 2025 5:59pm
next-seo-starter	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 26, 2025 5:59pm

[vercel]

@w0244079 is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

[denolia]

I had a similar issue

{"error":{"name":"PostgresError","severity_local":"ERROR","severity":"ERROR","code":"23505","detail":"Key (extname)=(uuid-ossp) already exists.","schema_name":"pg_catalog","table_name":"pg_extension","constraint_name":"pg_extension_name_index","file":"nbtinsert.c","line":"664","routine":"_bt_check_unique"}}

and was going to submit a similar fix, but you were first! :D Thank you for fixing it!

I'm not blocked but it might be confusing for other people. Hope this gets merged soon 🙏