[Tickets #7075] DB: Error no such field -- adding members to a group

bugs at horde.org bugs at horde.org
Thu Jul 17 03:27:07 UTC 2008


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

Ticket URL: http://bugs.horde.org/ticket/7075
------------------------------------------------------------------------------
  Ticket             | 7075
  Created By         | kkruger at tecs-company.com
  Summary            | DB: Error no such field -- adding members to a group
  Queue              | Horde Groupware
  Version            | 1.1.1
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


kkruger at tecs-company.com (2008-07-16 23:27) wrote:

hello,

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





More information about the bugs mailing list