Tickets :: [#7837] history adding records generates no alert if failed

6.0.0-beta1

7/8/25

Summary	history adding records generates no alert if failed
Queue	Horde Framework Packages
Queue Version	HEAD
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	jan (at) horde (dot) org
Requester	dom.lalot (at) gmail (dot) com
Created	01/12/2009 (6021 days ago)
Due
Updated	01/12/2009 (6021 days ago)
Assigned
Resolved	01/12/2009 (6021 days ago)
Milestone
Patch	Yes

01/12/2009 10:30:17 AM	Jan Schneider	Comment #3 Assigned to Jan Schneider State ⇒ Resolved	Reply to this comment
I decided to log the complete PEAR_Error instead. Thanks for the patch!

01/12/2009 10:29:33 AM	CVS Commit	Comment #2	Reply to this comment
Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/History/History.php?rt=horde&r1=1.62&r2=1.63&ty=u

01/12/2009 10:28:24 AM	Jan Schneider	Version ⇒ HEAD Queue ⇒ Horde Framework Packages

01/12/2009 08:03:45 AM	dom (dot) lalot (at) gmail (dot) com	Comment #1 Priority ⇒ 1. Low New Attachment: Nouveau Document texte.txt Patch ⇒ Yes Milestone ⇒ Queue ⇒ Horde Groupware Webmail Edition Summary ⇒ history adding records generates no alert if failed Type ⇒ Enhancement State ⇒ New	Reply to this comment
My SQL database was incorrectly migrated (horde_histories_seq id had a bad value) In fact, adding records generate duplicate keys (not properly returned by API as constraint errors). It would be great to add this patch so people can see there is a problem. If history is broken, syncml is broken too!