| Summary | Postgres error with interger column is empty |
| Queue | Kronolith |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | |
| Requester | cdc (at) ccicon (dot) com |
| Created | 04/30/2006 (7153 days ago) |
| Due | |
| Updated | 06/01/2006 (7121 days ago) |
| Assigned | 05/01/2006 (7152 days ago) |
| Resolved | 06/01/2006 (7121 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
testing, but currently am having other difficulties with the new
SyncML beta. Once I get past these issues, I will do some additional
testing on this issue.
Thanks!
CDC
State ⇒ Feedback
http://cvs.horde.org/diff.php/kronolith/lib/Driver/sql.php?r1=1.168&r2=1.169&ty=u
Thanks.
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Postgres error with interger column is empty
Queue ⇒ Kronolith
New Attachment: dud.txt
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.