Bug #1080

database migration does not preserve last update time

Added by don-dis-org-nz - 690 days ago. Updated 483 days ago.

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 1222
Added by scott 689 days ago

Add akismet timeout and better error handling. Closes #1080

History

03/10/2007 04:54 PM - neuro -

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF