Bug #1080
database migration does not preserve last update time
| Status : | Closed | Start : | ||
| Priority : | Low | Due date : | ||
| Assigned to : | scott - | % Done : | 0% |
|
| Category : | admin | |||
| Target version : | release2 | |||
| Resolution : | fixed |
Description
When I do a rake migrate to update my Typo database structure, often all the rows in the contents table are modified, changing the updated_at field to the current time. This makes services subscribing to my RSS/Atom feed show all my posts as having occurred in the last day. I've been fixing this with an UPDATE contents SET updated_at=created_at when I see it happen, but it's not ideal.
Associated revisions
Revision 15e814629ceedb8714a8a6ffc9637ee345744db3
Add akismet timeout and better error handling. Closes #1080
git-svn-id: http://svn.typosphere.org/typo/trunk@1222 820eb932-12ee-0310-9ca8-eeb645f39767
