mbucc
mbucc
Thanks for the detailed report, and glad you find it useful.
That looks pretty cool. I can see how it would simplify code and at the same time open many more databases up. And you already have to install a DB...
Holy shit, their supported database table now includes 27 different persistence backends, including a bunch of NoSQL ones. And its Go, so it runs on Windows ... I wonder if...
> > dont like this idea, I'm using shmig only to be able to use `\include` psql statement > in migrations, https://github.com/lib/pq doesn't support psql statements > My thought was...
I like it. :) This works nicely with your local config file patch. The only concern I can think of is if some user has non-migration SQL under a migration...
I agree this is a good feature. The TODO list is: * no new arguments---this should be the default behavior. * I want to move towards Posix compliance, not away...
If I stick with files, see https://github.com/Neilpang/acmetest/blob/master/letest.sh#L183-L200 for a solution from a script master.
Thanks for the bug report! Can you send me the insert statement triggering the range error? It should be the current epoch seconds, which currently is 1581270578. A MySQL signed...
Or just post your docker compose file.
Thank you. I'll take a closer look this weekend.