Consolidate dual ORM + dual DB setup (choose one DB strategy)

[dDevAhmed]

Overview

TypeORM and Prisma are both used against different SQLite files.

Why it is a problem

No cross-entity transactions, confusing migrations, mismatched environments.

Expected behavior

Single DB + consistent ORM/migrations.

Current incorrect behavior

Two ORMs, two DBs.

Suggested fix

• Decide on a single DB (Postgres recommended for production).
• Migrate schemas.
• Remove committed DB files and update docs/env.

Acceptance criteria

Only one DB connection in production; CI uses same setup.

Complexity

High

[snakefood3232]

I understand the challenge with using both TypeORM and Prisma across different SQLite files. I'd handle this by consolidating the setup to use Postgres with either Prisma or TypeORM, ensuring seamless migrations and consistent environment handling. I can have a PR ready within 3 days to address this transition. I've built unified database setups in full-stack applications before, which ensures smooth cross-entity transactions and simpler environment management.

[Yusufolosun]

@Yusufolosun has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hi Maintainer, Good day
Please can you entrust the implementation of this issue to me. I am a Full Stack Developer and I can deliver maintainable solution that align with your codebase

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Yusufolosun to this issue.

[spiffamani]

@spiffamani has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hey,

I'm a full-stack Software Engineer with 3 years of experience and a background in Blockchain development. I'm relatively new to open-source but I pick things up fast and I'm genuinely interested in this issue.
My main stack is React, TypeScript and Next.js on the frontend — I focus on clean component architecture, responsive design and performance. On the backend I work with Node.js, Java and Rust, handling everything from API design to database modeling.
A few things I've built:

https://www.zendvo.com/
https://cleanrest.vercel.app/

I'm comfortable jumping into an existing codebase, following conventions and shipping clean, maintainable code. My GitHub shows the kind of work I do better than I can describe it.
I'd love to take this on — thanks for considering me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @spiffamani to this issue.

[Ekenesamuel8]

@Ekenesamuel8 has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hello maintainer. I will love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ekenesamuel8 to this issue.

[AbdulSnk]

@AbdulSnk has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hello, I would like to work on this issue. I read the issue description carefully, i will implement the solution as soon as the issue is assigned to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AbdulSnk to this issue.

[drips-wave]

Congratulations, @AbdulSnk! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @AbdulSnk: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊