PlanetScale workflow confuses me
So, I'm not even sure if I should be doing this, but I'm working with a few people on a T3 project and we chose to use PlanetScale (free tier) due to the simplicity.
However, as we modify the database, we realize how the workflow doesn't seem to make sense, so we have been wondering if we're doing anything wrong.
As we are using it free for now, we only have one Dev branch, so we all work on it and deploy the changes.
But the thing is, if person A is working on the schema with, let's say, the table
To mitigate that, we do
However, as we modify the database, we realize how the workflow doesn't seem to make sense, so we have been wondering if we're doing anything wrong.
As we are using it free for now, we only have one Dev branch, so we all work on it and deploy the changes.
But the thing is, if person A is working on the schema with, let's say, the table
Clients, and the person B works on a schema without that table, what happens is that when person B does the npx prisma db push, they'll override the version with the table and everything will crash.To mitigate that, we do
npx prisma db pull before the push aaand.. that's where the problem is. Since it's the same branch, we can't really "merge" the differences, so when the person A does a pull, it would erase the Clients table either way.