Moving to MongoDB from PostgreSQL: migrations required? #7795
Unanswered
DavidOliver
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been using PostgreSQL in dev with Payload v2, but I might try using MongoDB as I've come across a couple of issues with database updates when updating Payload. I don't need to keep any data from PostgreSQL.
Am I right in thinking that, for a new project in production, database migrations are not required when using MongoDB in the way they are for PostgreSQL, and that new sections' and fields' data will simply be created as documents in MongoDB as required? Having configured MongoDB, I've run the create migration command with my sections and fields set up, and have only empty up and down functions. I think migrations for MongoDB will only be required if I'm, for example, changing a field name and need the data to be preserved?
Or maybe I should wait for Payload v3 with its official full PostgreSQL support?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions