Timeline for Two database fields for date and time - should they be merged?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 29, 2012 at 8:40 | vote | accept | m-smith | ||
| May 15, 2012 at 12:34 | comment | added | mjfgates | mmm, yes. Triggers. At least until the axe falls... :) | |
| May 15, 2012 at 8:10 | vote | accept | m-smith | ||
| May 15, 2012 at 8:10 | |||||
| May 14, 2012 at 18:32 | comment | added | Blrfl | And don't forget to add triggers that update the old columns when the new one changes and vice versa. | |
| May 14, 2012 at 16:26 | comment | added | Doc Brown | +1. Thats exactly what I was going to suggest (with the exception that I would call the new column MONKEY_DATETIME). | |
| May 14, 2012 at 16:01 | history | answered | mjfgates | CC BY-SA 3.0 |