-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Updates to a collection #290
Comments
Completely agree, can we have an update on when can we expect this functionality or if there is any workaround for this at the moment? |
Just like we have examples for insertOne() and insertMany() https://docs.liquibase.com/install/tutorials/mongodb.html. |
While there is not a bespoke change type for updates, you can do updates by leveraging the runCommand change type in a changeset. It follows the pattern from Mongo's runCommand() function, so for For example:
|
Any plan on providing support for this without runCommand() ? |
We are planning that plan right now and looking at different ways to do that. How do you envision an instruction such as this being handled? We would love to hear your thoughts. |
You can do most of what is needed with runCommand or adminCommand. These make the specific operators such as insertMany() redundant. However, similar to plain SQL changes for relational systems (https://www.liquibase.com/blog/plain-sql) it could be neat to have plain-MQL feature added |
I am not seeing the value of using Liquibase for MongoDB if I have to build my own update solution around the runCommand. For consistency, I would just build my solution to use the runCommand for all activities. The only thing I would be missing is the change log management that Liquibase provides, but that is all arbitrary in this context. |
It appears that the extension is missing the ability to update a collection. How is everyone else on the planet solving the absence of updates while still using Liquibase for automated mongoldb deployments? This is to be a huge feature missing from the extension.
The text was updated successfully, but these errors were encountered: