Timeline for How to handle a one-time startup SQL script
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2016 at 21:52 | comment | added | Nick Gotch | @user2669338 That makes sense, I'm looking into seeing if we can do that. | |
| May 21, 2016 at 10:20 | comment | added | user2669338 | Shouldn't this be done as part of the deployment process? | |
| May 21, 2016 at 7:11 | answer | added | blm768 | timeline score: 0 | |
| May 19, 2016 at 19:42 | history | tweeted | twitter.com/StackProgrammer/status/733382230848966656 | ||
| May 19, 2016 at 18:33 | comment | added | Jules | I haven't ever done this with mysql, so maybe it won't work, but why can you not simply use transactions to isolate the instances from each other? The first instance to commit a transaction will get it to work, the others will fail because the definition of the tables has changed and the columns it would work with are no longer there, which error it can then happily ignore. | |
| May 19, 2016 at 18:06 | answer | added | Robert Harvey | timeline score: 3 | |
| May 19, 2016 at 15:03 | history | asked | Nick Gotch | CC BY-SA 3.0 |