You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Drizzle team! We're big fans of the project and excited about deeper adoption.
We're migrating a service from Go to TypeScript in phases: the new TS service will have read-only DB access initially, then we'll progressively move write authority resource-by-resource. During this transition, we'll need to model tables in both Drizzle and our existing Go migration system.
Question: If we adopt Drizzle for migration management now (pre-v1), how much migration effort should we expect when v1 is released? Would it be simpler to wait until v1 before switching migration authority to Drizzle?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Drizzle team! We're big fans of the project and excited about deeper adoption.
We're migrating a service from Go to TypeScript in phases: the new TS service will have read-only DB access initially, then we'll progressively move write authority resource-by-resource. During this transition, we'll need to model tables in both Drizzle and our existing Go migration system.
Question: If we adopt Drizzle for migration management now (pre-v1), how much migration effort should we expect when v1 is released? Would it be simpler to wait until v1 before switching migration authority to Drizzle?
Thanks for any guidance!
Beta Was this translation helpful? Give feedback.
All reactions