Problem: One vercel's postgres, and need a way to use it in multiple projects

[iyxan23]

Question

Hey all!

I'm just going to go to the point, I have a single free vercel plan that only allows to have one postgres database. I'm thinking of using that one database for multiple projects at once with each its own different prisma schemas.

I've renamed all each and every of the tables on each schemas to have a prefix. But as I tried to deploy to vercel (which has prisma db push as its postinstall script), prisma asked me to drop these tables.

Is there a way to prevent prisma from deleting these tables, and just let them be?

(there are no conflicting table names)

Would really appreciate quick answers, I'm quite in a hurry right now! Thank you!

How to reproduce (optional)

Expected behavior (optional)

No response

Information about Prisma Schema, Client Queries and Environment (optional)

• OS: Fedora 38
• Database: PostgreSQL
• Node.js version: v20.8.1
• Prisma version dump:

  prisma                  : 5.4.2
  @prisma/client          : 5.4.2
  Current platform        : rhel-openssl-1.1.x
  Query Engine (Node-API) : libquery-engine ac9d7041ed77bcc8a8dbd2ab6616b39013829574 (at node_modules/@prisma/engines/libquery_engine-rhel-openssl-1.1.x.so.node)
  Schema Engine           : schema-engine-cli ac9d7041ed77bcc8a8dbd2ab6616b39013829574 (at node_modules/@prisma/engines/schema-engine-rhel-openssl-1.1.x)
  Schema Wasm             : @prisma/prisma-schema-wasm 5.4.1-2.ac9d7041ed77bcc8a8dbd2ab6616b39013829574
  Default Engines Hash    : ac9d7041ed77bcc8a8dbd2ab6616b39013829574
  Studio                  : 0.494.0
  

[janpio]

No. You will probably have better success using one schema per project.

[keeandev]

Question

Hey all!

I'm just going to go to the point, I have a single free vercel plan that only allows to have one postgres database. I'm thinking of using that one database for multiple projects at once with each its own different prisma schemas.

I've renamed all each and every of the tables on each schemas to have a prefix. But as I tried to deploy to vercel (which has prisma db push as its postinstall script), prisma asked me to drop these tables.

Is there a way to prevent prisma from deleting these tables, and just let them be?

(there are no conflicting table names)

Would really appreciate quick answers, I'm quite in a hurry right now! Thank you!

How to reproduce (optional)

Expected behavior (optional)

No response

Information about Prisma Schema, Client Queries and Environment (optional)

• OS: Fedora 38
• Database: PostgreSQL
• Node.js version: v20.8.1
• Prisma version dump:

  prisma                  : 5.4.2
  @prisma/client          : 5.4.2
  Current platform        : rhel-openssl-1.1.x
  Query Engine (Node-API) : libquery-engine ac9d7041ed77bcc8a8dbd2ab6616b39013829574 (at node_modules/@prisma/engines/libquery_engine-rhel-openssl-1.1.x.so.node)
  Schema Engine           : schema-engine-cli ac9d7041ed77bcc8a8dbd2ab6616b39013829574 (at node_modules/@prisma/engines/schema-engine-rhel-openssl-1.1.x)
  Schema Wasm             : @prisma/prisma-schema-wasm 5.4.1-2.ac9d7041ed77bcc8a8dbd2ab6616b39013829574
  Default Engines Hash    : ac9d7041ed77bcc8a8dbd2ab6616b39013829574
  Studio                  : 0.494.0
  

If you're looking to solve this issue a different way, try this out: https://orm.drizzle.team/docs/goodies#multi-project-schema

[iyxan23]

yes! I switched to drizzle and it was a breeze. In case anyone else is attempting to do the same thing, use drizzle instead.

[keeandev]

Totally!

[KadaGuetouache]

I haven't tried it yet but also prisma allows for multi-project-schema prisma-muliple-schema