My thinking on MongoDB mocks is that, since it's a database, it should largely parallel MySQL (except where the difference between the two is relevant, if there are any).
Do any services use migrations on a MongoDB? Presumably they don't need them to create collections as collections are schema-less or not strongly typed or however you want to put it, but theoretically a service could set up initial data. (As with #46, it might make sense to allow defaults to be applied by Touchstone after the service rather than before it.)
This scenario seems relatively unlikely given the use cases for Mongo, and therefore low priority; however, I wanted to bring up matching MySQL behavior/options in general.
My thinking on MongoDB mocks is that, since it's a database, it should largely parallel MySQL (except where the difference between the two is relevant, if there are any).
Do any services use migrations on a MongoDB? Presumably they don't need them to create collections as collections are schema-less or not strongly typed or however you want to put it, but theoretically a service could set up initial data. (As with #46, it might make sense to allow defaults to be applied by Touchstone after the service rather than before it.)
This scenario seems relatively unlikely given the use cases for Mongo, and therefore low priority; however, I wanted to bring up matching MySQL behavior/options in general.