Skip to main content

Timeline for Staging MySQL databases

Current License: CC BY-SA 3.0

9 events
when toggle format what by license comment
Feb 3, 2016 at 2:47 comment added Vérace Hierarchy is your answer. Mine would be db no.1, app 2nd. Work from there. en.m.wiktionary.org/wiki/one_who_hesitates_is_lost. Fix the db at point x, then insist the app passes regression from there. Get db x and app x in sync, then move on to new branches.
Feb 3, 2016 at 2:40 comment added Scott Deerwester Thanks for the comments. Very helpful for the FK issue. I'm going to leave the question up to see if I can get some feedback on the rest of the question, particularly what's involved in staging as described.
Feb 3, 2016 at 1:05 comment added Vérace performance_schema should help.
Feb 3, 2016 at 0:36 answer added Rick James timeline score: 1
Feb 2, 2016 at 22:43 comment added Scott Deerwester I can certainly do it manually, but I've got dozens of databases that I'm importing, all updated whenever the maintainer feels like it, so it's a much better idea to script the updates. A manual step turns a daily five minute task into a half an hour.
Feb 2, 2016 at 22:18 comment added Vérace Try checking out the information_schema (don't have MySQL running). But, if you don't change the schema, can't you do it once even manually? Also Google "find foreign keys in schema mysql"
Feb 2, 2016 at 19:50 comment added Scott Deerwester Is there a way to retrieve a list of pairs of (source, target) table pairs for all foreign keys in a database?
Feb 2, 2016 at 19:08 comment added Vérace What about deleting the tables with FK dependencies in reverse order of dependency - i.e. those at the bottom of the chain first?
Feb 2, 2016 at 16:37 history asked Scott Deerwester CC BY-SA 3.0