Timeline for Trouble with triggers and insert .. on duplicate key update
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 24, 2014 at 23:13 | comment | added | ypercubeᵀᴹ | Yes, sorry, I didn't really read the first paragraph. I couldn't manage to reproduce though the behaviour you describe. I created these identical tables and everything goes well. And I just noticed the answer ;) | |
| Jan 24, 2014 at 20:56 | comment | added | atxdba | @ypercube I believe my opening statement declared the reason. Reworded, they are not exactly the same, one table has a shorter retention period and the other was more of an all time historical table | |
| Jan 24, 2014 at 20:54 | vote | accept | atxdba | ||
| Jan 24, 2014 at 20:54 | answer | added | atxdba | timeline score: 2 | |
| Jan 24, 2014 at 13:30 | comment | added | ypercubeᵀᴹ |
I don't understand why you would want this behaviour. It seems you want to have the 2 tables having exactly the same data (well, as long as nothing is deleted from main_table.)
|
|
| Nov 25, 2013 at 8:26 | answer | added | Abhik Dey | timeline score: 0 | |
| Dec 11, 2012 at 21:44 | history | edited | Derek Downey | CC BY-SA 3.0 |
added formatting for the quote from the docs
|
| Dec 11, 2012 at 18:44 | history | asked | atxdba | CC BY-SA 3.0 |