6.0.0-git
2019-04-21

[#7837] history adding records generates no alert if failed
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 2009-01-12 (3751 days ago)
Due
Updated 2009-01-12 (3751 days ago)
Assigned
Resolved 2009-01-12 (3751 days ago)
Milestone
Patch Yes

History
2009-01-12 10:30:17 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!
2009-01-12 10:29:33 CVS Commit Comment #2 Reply to this comment
2009-01-12 10:28:24 Jan Schneider Version ⇒ HEAD
Queue ⇒ Horde Framework Packages
 
2009-01-12 08:03:45 dom (dot) lalot (at) gmail (dot) com Comment #1
Type ⇒ Enhancement
State ⇒ New
Priority ⇒ 1. Low
Summary ⇒ history adding records generates no alert if failed
Queue ⇒ Horde Groupware Webmail Edition
Milestone ⇒
Patch ⇒ Yes
New Attachment: Nouveau Document texte.txt Download
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!

Saved Queries