[Tickets #3857] NEW: Postgres error with interger column is empty

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=3857
-----------------------------------------------------------------------
 Ticket             | 3857
 Created By         | cdc at ccicon.com
 Summary            | Postgres error with interger column is empty
 Queue              | Kronolith
 Version            | HEAD
 State              | Unconfirmed
 Priority           | 2. Medium
 Type               | Bug
 Owners             | 
+New Attachment     | dud.txt
-----------------------------------------------------------------------


cdc at ccicon.com (2006-04-30 15:27) wrote:

I have discovered a bug in the handling of empty integer values when a
postgres backend is being used instead of a mysql backend.  I discovered
this problem as a result of a SyncML insert into the kronolith tables.  The
evert_alert field is being fed an empty string ('') rather than a NULL. 
Although mysql will accept this syntax, postgres will not.  I have attached
the error message from the horde logs.

I'm not positive this is a kronolith bug, or if this should be fixed at the
PEAR_DB level.  I believe it should be fixable in the SyncML code by
replacing '' with NULL for interger columns, however, there are likely
other, non SyncML scenarios which might triger this same problem.