Opened 10 years ago
Closed 9 years ago
#1072 closed defect (fixed)
[API] Updated objects don't have "updated" field
| Reported by: | JanKusanagi | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | programming | Keywords: | api, timestamps |
| Cc: | Parent Tickets: |
Description
This is probably quite low priority, but for completeness sake, objects should have a "updated" field in addition to the "published" field, when said objects have been updated at least once, as Pump.io objects have.
Hopefully the DB already has that info, and it's only a matter of showing it via API.
Change History (3)
comment:1 by , 10 years ago
comment:2 by , 9 years ago
I think this has been fixed, can you let me know if you think it's been fixed or if you still don't see the updated field.
comment:3 by , 9 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The database unfortunately does not store the updated time and only the time the object was created. The few places I have included the updated attribute it's actually the created attribute that doesn't change upon update. I will be adding a updated timestamp to all objects when I make the database changes and in a migration older objects will simply have this field populated with the creation/publication date.