fix: fix too many clients error on Postgres due to HMR with Drizzle

[fuegoio]

✅ Checklist

• I have followed every step in the contributing guide (updated 2022-10-06).
• The PR title follows the convention we established conventional-commit
• I performed a functional test on my final commit

---

Changelog

• Add a singleton for Postgres connection with Drizzle to avoid creating a new connection on every Hot Reload

---

With Drizzle and a Postgres connection, we always had the issue of having too many clients already because of the HMR (see https://www.answeroverflow.com/m/1146224610002600067).

Having a singleton to fix that seems to be the best way.

Happy to implement this logic on other databases if needed, or write some tests, but I did not know if the approach would be accepted!

Thanks for your work :)

[changeset-bot]

🦋 Changeset detected

Latest commit: 011de02

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
create-t3-app	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
create-t3-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 1, 2024 4:28pm

[vercel]

@fuegoio is attempting to deploy a commit to the t3-oss Team on Vercel.

A member of the Team first needs to authorize it.

[juliusmarminge]

Should we use a similar pattern that we do for prisma to keep code consistency?

https://github.com/t3-oss/create-t3-app/blob/main/cli/template/extras/src/server/db/db-prisma.ts

[fuegoio]

Should we use a similar pattern that we do for prisma to keep code consistency?

https://github.com/t3-oss/create-t3-app/blob/main/cli/template/extras/src/server/db/db-prisma.ts

You're right I did not see it sorry, changed it on all drizzle databases as well for consistency.

[juliusmarminge]

LGTM - asked the Drizzle team for their opinion on the change too so will wait with merge until I hear back from them

[fuegoio]

Changed it to only cache the connection instead of the whole drizzle client instance, clearer you are right ;)