Uploaded image for project: 'Mongoid'
  1. Mongoid
  2. MONGOID-1826

created_at *exactly* equals updated_at on new records

    • Type: Icon: Task Task
    • Resolution: Done
    • 12_01_17
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      currently mongoid sets updated_at and created_at incorrectly on new records. that is to say they are different by a handful of milliseconds when, in fact, they should be precisely the same for new records. i recently hit this issue looking for records that had been updated ever: aka created_at!=updated_at and was sad to see that the small difference semantically means that all my database records have, apparently, been updated at some point when, in fact, they have not. this small patch fixes this behavior. up next is a patch that implements transactions for mongoid and marks all records created inside one with the same timestamp

            Assignee:
            Unassigned Unassigned
            Reporter:
            ahoward ara.t.howard
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: