Any wayt to avoid all downtime with prisma?
Back whenever, with hibernate when we dropped columns, we would 1. deploy app that no longer reads/writes columns and 2. run migration while live app is running to drop columns.
Voila - no downtime for customers.
In prisma, does this work? I suspect we keep adding breaking changes and doing this wrong but then I add a few columns locally and one of my other servers locally hitting same DB BREAKS!!!
This second scenarios is
1. run migration - old servers should work but seem not to
2. deploy app that uses new columns
hibernate worked great in this case but in this second case, I add columns (nullable at first) and it seems to break things. I may need to pay closer attention but putting this out there in case others see this behavior before I go down a rabbit hole investigation(ie. some prelim knowledge of what way it works would be nice).
Voila - no downtime for customers.
In prisma, does this work? I suspect we keep adding breaking changes and doing this wrong but then I add a few columns locally and one of my other servers locally hitting same DB BREAKS!!!
This second scenarios is
1. run migration - old servers should work but seem not to
2. deploy app that uses new columns
hibernate worked great in this case but in this second case, I add columns (nullable at first) and it seems to break things. I may need to pay closer attention but putting this out there in case others see this behavior before I go down a rabbit hole investigation(ie. some prelim knowledge of what way it works would be nice).
