id summary reporter owner description type status priority milestone component version severity resolution keywords cc branch changelog apichanges internalchanges 6466 Ticket.save_changes() timestamp precision is too low... tumma72@… Remy Blank "When updating a Ticket, calling the save_changes method, the changed fields are stored into the table ticket_change, which has a key formed by (ticket, time, field). Consider the scenario where using a ITicketChangeListener you want to manipulate and change one of the just changed fields, and call again on the ticket the method save_changes...[[BR]] [[BR]] Most likely it happen within the same second, and you get the error:[[BR]] {{{ERROR: duplicate key violates unique constraint ""ticket_change_pk""}}} [[BR]] It would be better to use datetime.now() that has also microseconds has key... " defect closed normal 0.12 ticket system 0.10-stable normal fixed needmajor felix.schwarz@… direvus@…