If one of the many schema migration solutions out there doesn't work for you, hacking one together is simple enough: * Put your schema&#...
If one of the many schema migration solutions out there doesn't work for you, hacking one together is simple enough: * Put your schema/data migrations into .sql files as raw SQL * Number the files from 0001 on * Write a script to apply each migration file to the DB in order, recording the file name to a log table after successful application. Only apply migrations not found in the log table. * Commit your .sql migration files along with the code it is tied to.
Posted by lastofus on Jul 20, 2015, 5:25 PM
Tags
Related issues
- > Because they don't believe the disasters were inflicted by them.
- Hehe, yeah I'm not sure when John Stewart would have worked there or what the pain points were for him, but he worked there for a bit.
- https://www.apple.com/shop/product/mxcl3ll/a/magic-keyboard-...
- If first-order hybrids made up only a small proportion of the total population of humans and Neanderthals, then the probability that a pa...
- Well, I'd be interested to hear what some of those nuances are, personally.
- My biggest Amazon annoyance.
Raise real-world problems, find people facing the same issue, and discuss solutions.5,500 issues0 comments
hackernews (E-commerce)
> Because they don't believe the disasters were inflicted by them.
Hehe, yeah I'm not sure when John Stewart would have worked there or what the pain points were for him, but he worked there for a bit.
https://www.apple.com/shop/product/mxcl3ll/a/magic-keyboard-...
If first-order hybrids made up only a small proportion of the total population of humans and Neanderthals, then the probability that a pa...
Well, I'd be interested to hear what some of those nuances are, personally.
My biggest Amazon annoyance.
> There's not really an unmet need for innovation in broadband delivery; the issue is running new wires broadband has costs, and in a lot...
Speaking of Amazon's account process, I have a really annoying problem with theirs.
If one of the many schema migration solutions out there doesn't work for you, hacking one together is simple enough: * Put your schema&#...
If one of the many schema migration solutions out there doesn't work for you, hacking one together is simple enough: * Put your schema/data migrations into .sql files as raw SQL * Number the files from 0001 on * Write a script to apply each migration file to the DB in order, recording the file name to a log table after successful application. Only apply migrations not found in the log table. * Commit your .sql migration files along with the code it is tied to.
Comments (0)
No comments yet. Start the discussion.