Timeline for Do you store mysql exports in your version control tool for reverting to in event of error?
Current License: CC BY-SA 2.5
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 3, 2011 at 12:37 | vote | accept | therobyouknow | ||
| Feb 1, 2011 at 19:33 | comment | added | therobyouknow | +1 This approach gives fine granularity but still the same safety of controlling the whole database stage outside of the database itself. Safety because the database itself isnt used to version control itself - it could get corrupted, rather this is done externally. Fine granularity because each change can be recognised rather than a complete snapshot containing everything. Also because this is a working solution - it must be some feet to get the "undo" side of a change working. | |
| Feb 1, 2011 at 19:27 | comment | added | therobyouknow | That's what I would be looking for - something independent of the database. Contrast with an in-situ version control that is not immune to a faulty piece of code corrupting the whole database including the version history. | |
| Feb 1, 2011 at 15:07 | history | edited | DBlackborough | CC BY-SA 2.5 | corrected some spelling |
| Feb 1, 2011 at 15:00 | history | answered | DBlackborough | CC BY-SA 2.5 |