[Tickets #7092] Query's from Drivers/SQl.php incompatibility with Mysql 5

bugs at horde.org bugs at horde.org
Tue Jul 22 13:04:50 UTC 2008


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

Ticket URL: http://bugs.horde.org/ticket/7092
------------------------------------------------------------------------------
  Ticket             | 7092
  Created By         | lauren at servicom2000.com
  Summary            | Query's from Drivers/SQl.php incompatibility with
                     | Mysql 5
  Queue              | Kronolith
  Version            | 2.2
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


lauren at servicom2000.com (2008-07-22 09:04) wrote:

We have errors like thi on horde.log;
Jul 22 14:39:54 HORDE [error] [kronolith] DB Error: syntax error:  
SELECT event_id, event_uid, calendar_id, event_description,  
event_location, event_private, event_status, event_attendees,  
event_keywords, event_title, event_category, event_recurcount,  
event_recurtype, event_recurenddate, event_recurinterval,  
event_recurdays, event_start, event_end, event_alarm, event_modified,  
event_exceptions, event_creator_id FROM kronolith_events WHERE  
event_uid = ? AND calendar_id IN (?) [nativecode=1064 ** You have an  
error in your SQL syntax; check the manual that corresponds to your  
MySQL server version for the right syntax to use near '? AND  
calendar_id IN (?)' at line 1] [pid 29998 on line 435 of  
"/var/www/horde/kronolith/lib/Driver/sql.php"]

when we sync calendar, the enevnts are inserted in the database, but  
you have error on server.

We have made simple querys like:

SELECT event_uid FROM kronolith_events WHERE event_uid = ?;
ERROR 1064 (42000): You have an error in your SQL syntax; check the  
manual that corresponds to your MySQL server version for the right  
syntax to use near '?' at line 1

and have the same error.

This is our Mysql version

MYSQL VERSION: mysql  Ver 14.12 Distrib 5.0.51a








More information about the bugs mailing list