eGroupware ProjectManager doesn't work properly with PostgreSQL
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
egroupware (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: egroupware
I've been using eGroupware 1.6 (backported from karmic to hardy by the eBox project) in eBox for a while now, and I've come across a couple of nasty bugs in ProjectManager. I've been discussing these issues on eBox forums and I've read similar bug reports and patch proposals on eGroupware forums:
- After adding about 10 subprojects, some of them are incorrectly displayed as mainprojects.
- Searching doesn't work at all but instead just spews out PostgreSQL errors (ERROR: operator does not exist: integer ~~* unknown) which are seemingly impossible to get rid of without logging out of eGroupware.
Both of them are PostgreSQL-related, and apparently are not a problem when running eGroupware on a MySQL database. I fixed the first bug manually by changing some CASTs from CHAR to VARCHAR. See complete description and proposed fix here:
http://
The search bug seems more complex so unfortunately I failed to fix it, even though it's probably just another incompatible CAST somewhere. Here's some information about it:
http://
The eGroupware website recommends upgrading to 1.6.002 ASAP due to security issues, but apparently those PostgreSQL-related patches should be included in the Ubuntu package, because PostgreSQL is the default database for egroupware.
Ubuntu version: Ubuntu 8.04.3 LTS
egroupware version: 1.6.001+
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.