Timeline for what is the fast way to prepare test db? slimming mysql db
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 26, 2016 at 6:39 | comment | added | Sławomir Lenart | @Rick James: Slimming here is an inter-state for preparing test environment - we want loading a specific, known set of data, then generate fixtures (programming objects/code/json/...) based on that data. After all these fixtures (serialized db data in code) will be loaded (as new database) and modified by tests again and again. It's crucial to have fast running tests. In my db I have exactly 949 tables with thousands or millions records each, but for tests I need only dozens/hundreds records in each table. | |
| Aug 26, 2016 at 3:12 | comment | added | Rick James | What is the advantage of slimming? With good indexes, performance is unlikely to improve noticeably. | |
| Aug 25, 2016 at 14:19 | history | tweeted | twitter.com/StackDBAs/status/768815166574235648 | ||
| Aug 25, 2016 at 14:14 | answer | added | O. Jones | timeline score: 0 | |
| Aug 25, 2016 at 14:08 | history | migrated | from stackoverflow.com (revisions) | ||
| Aug 25, 2016 at 14:01 | comment | added | ups | .... and you can freeze time in tests, so don't worry about state. | |
| Aug 25, 2016 at 13:59 | comment | added | ups | There is acceptable, db has hundreds of tables and writing fixtures from scratch for every possible request type will be really time consuming. The problem is how to examine access coverage in mysql ? and then how to use that coverage to remove everything else ? btw - it could have usage in different purpose as well. | |
| Aug 25, 2016 at 13:52 | comment | added | Bernd Buffen | you cant do it so easy. If you have query like : SELECT .... WHERE datefield > NOW() - interval 1 DAY . So it works only today. | |
| Aug 25, 2016 at 13:41 | history | asked | Sławomir Lenart | CC BY-SA 3.0 |