Matt
Matt
> if I understand correctly, then go code would know which db driver is in use, migrate assumes the migrations in a directory are homogeneous. meaning you will need one...
yeah, symlinks should work.
Thanks for your PR. I think the tests are failing somewhere else actually. Need to investigate as well.
@JensRantil thanks for your PRs. I closed #280 in favor of this one. I'd much rather find a regex than introducing custom query markup. (Partially related: [FAQ:why-two-separate-files](https://github.com/mattes/migrate/blob/master/FAQ.md#why-two-separate-files-up-and-down-for-a-migration)) @syndbg and @JensRantil...
> Cannot allocate memory I think the machine is just out of memory.
Could you open a PR with improved documentation? Right now there are some examples here: https://github.com/mattes/migrate/tree/master/database/postgres/examples/migrations Does that help and eventually help fixing the parsing error?
If you're asking "user guide/ manual". We don't have anything like that so far.
It just creates empty sql files with the correct naming convention. What are you expecting to see as the content?
Can you give an example?
Isn't that highly opinionated though? Here is another problem (which could be solved). The create command doesn't know about the driver, so the Postgres example wouldn't make sense for mongodb...