Timeline for MySQL replication: "Houston, We've Got a Problem"
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 17, 2012 at 10:25 | comment | added | Katafalkas | Cheers for a reply, I'll check out the query logging. | |
| Feb 16, 2012 at 1:38 | comment | added | atxdba | Instead of being so draconian w/ the devs, give them guidance an pointers as needed. Hopefully they're smart or they wouldn't have been hired as devs to begin with. To audit the finer points of their queries you might just turn on general query logging in your qa/dev environment. Look through that for new and potentially suspect queries. Raise true issues you might find from that rather than making them hate you for wanting to review ever select column from table where primary_key=N; query | |
| Feb 15, 2012 at 16:44 | comment | added | Katafalkas | totally agree. After this incident, I ll try making all the programers to show me, and test all their "awesome" queries before putting the production. Cheer for info! much appreciated. | |
| Feb 15, 2012 at 16:16 | history | answered | atxdba | CC BY-SA 3.0 |