Summary | DB: Error no such field -- adding members to a group |
Queue | Horde Groupware |
Queue Version | 1.1.1 |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | chuck (at) horde (dot) org |
Requester | kkruger (at) tecs-company (dot) com |
Created | 2008-07-17 (4568 days ago) |
Due | |
Updated | 2008-07-17 (4568 days ago) |
Assigned | |
Resolved | 2008-07-17 (4568 days ago) |
Milestone | |
Patch | No |
must be a PEAR issue, not postgresql database,... I usually do the
same syntax as in the original file.
hmmm, is there a qualified solution in PEAR?
Klaus Kruger
TECS Company Inc
15 Eury Lane
Somerset KY 42501
606-451-3005
Assigned to Chuck Hagenbuch
State ⇒ Resolved
in CVS and for 3.2.2 - thanks!
http://cvs.horde.org/diff.php/framework/Group/Group/sql.php?r1=1.7&r2=1.8&ty=u
http://cvs.horde.org/diff.php/horde/docs/CHANGES?r1=1.1127&r2=1.1128&ty=u
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ DB: Error no such field -- adding members to a group
Queue ⇒ Horde Groupware
Milestone ⇒
Patch ⇒ No
I have been trying to track down why I was getting 'DB: Error no such
field' when trying to add members to a group in horde-groupware-1.1.1.
I'm still very new to horde and am still trying to learn my way
around, but there is no mention of this error in /tmp/horde.log. I
was however able to get postgresql to log this error:
In horde/lib/Horde/Group/sql.php, I made the following change, and
members were successfully added to the group.
880 if (!empty($this->data['users'])) {
881 $query = 'INSERT INTO horde_groups_members
(group_uid, user_uid)'
882 .' VALUES (' . $this->id . ', ?)';
882 // original line .' VALUES ("' . $this->id . '", ?)';
883 $sth = $this->_groupOb->_write_db->prepare($query);
884 $result =
$this->_groupOb->_write_db->executeMultiple($sth,
array_keys($this->data['users']));
885 if (is_a($result, 'PEAR_Error')) {
886 return $result;
887 }
888 }
The database is postgresql 8.1.11-1.el5_1.1 if that means anything.
I would appreciate if this find can be confirmed,... or maybe I have
something set up wrong to cause this behaviour. The reason I say that
is that during the horde setup I used the default encoding of
ISO_8859_1. In postgresql I also left the default of UTF8.
I wonder if this may be part of it.
Klaus