Brion Vibber 9ec395b07a Workaround for reply timeline since_id issue: save the notice.created value into reply.modified, so we can key off it as expected.
As a hack this removes the mysql_timestamp bit from the field settings on reply.modified so that our value actually gets saved. This *should* work ok as long as system timezone is set correctly, which we now set to UTC to match when connecting.
2011-02-25 13:22:13 -08:00
..
2011-02-03 10:46:56 -05:00
2011-02-03 12:04:54 -05:00
2010-09-20 20:40:55 +02:00
2011-02-03 10:51:59 -05:00
2011-02-03 11:28:39 -05:00
2011-02-10 12:04:13 -08:00
2011-02-03 11:30:14 -05:00