Timeline for Database log_* tables are all empty in production, but not when I export the database for testing in an identical setup
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 5, 2014 at 22:27 | answer | added | jesseconnr | timeline score: 2 | |
| Dec 13, 2013 at 15:20 | comment | added | jesseconnr | The tables are empty on prod_db and yes, --add-drop-database drops the entire dev_db when I import it in. The moment I visit the dev site after importing the database the entries into the log_* tables begin. The online customer section starts working as well, due to the fact that the log_* tables start working. | |
| Dec 12, 2013 at 21:04 | comment | added | Peter O'Callaghan |
Isn't the default behaviour of mysqldump to output DROP TABLE IF EXISTS for each table? So I imagine that can't be the issue. EDIT: Just realised they're using --add-drop-database.
|
|
| Dec 12, 2013 at 20:33 | comment | added | Alana Storm |
I don't see anywhere that you've dropped the contents of dev_db — which means if you've ever loaded up that database with log entries they'll stick around.
|
|
| Dec 12, 2013 at 20:01 | review | First posts | |||
| Dec 12, 2013 at 20:16 | |||||
| Dec 12, 2013 at 19:52 | history | edited | jesseconnr |
edited tags
|
|
| Dec 12, 2013 at 19:46 | history | asked | jesseconnr | CC BY-SA 3.0 |