Feature ideas and requests #125
Replies: 2 comments 3 replies
-
Hey, thanks for your work on this package! I'm wondering why the cli down <migration-name> roll back migrations down to given name Is that a design decision you feel strongly about? A natural feature would be to allow users to omit the argument. In which case, only the latest migration would be rolled-back. This is commonly supported by other migration tools -- although I've not surveyed the alternatives for mongoose. Let me know what you think 🙂 |
Beta Was this translation helpful? Give feedback.
-
thanks for creating this awesome package! Question: Is it currently possible to maintain the migrations collection in a separate database than the one in which the migrations are being run. Say we have a use case for having multiple databases that use the exact same collections/schemas. Lets call these databases a, b, and c. Is it possible to maintain the migrations collection centrally in a separate database d, while running migrations on databases a, b, and c? |
Beta Was this translation helpful? Give feedback.
-
Let me know if you like current state of the package and if you want to improve something
Beta Was this translation helpful? Give feedback.
All reactions