phplist

NOTE:: Before reporting an issue, make sure you are running the latest version, currently 3.3.1


View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0015394phplist applicationMessage Send Processpublic20-12-09 14:4420-01-10 14:47
Reporteradrian15 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product VersionFutureDevelopments 
Target VersionFixed in Version4.0.x 
Summary0015394: processqueue database 1064 error near interval
DescriptionWe are using phplist svn revision 1703.

Whenever we try to process message queue (processqueue.php) we get the following error:

Database error 1064 while doing query 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 'interval) as newembargo , current_timestamp + cast(repeatinterval || ' minute' ' at line 1

However the message is sent succesfully.
Additional InformationI suppose the message has something to do with these lines of code at connect.php:
  $query
  = 'select *'
  . ' , embargo + cast(repeatinterval || \' minute\' as interval) as newembargo'
  . ' , current_timestamp + cast(repeatinterval || \' minute\' as interval) as newembargo2'
  . ' , current_timestamp < embargo + cast(repeatinterval || \'minute\' as interval) as isfuture'
  . ' from %s'
  . ' where id = ?'
  . ' and current_timestamp < repeatuntil';
  $query = sprintf($query, $GLOBALS['tables']['message']);
  $rs = Sql_Query_Params($query, array($msgid));
  $msgdata = Sql_Fetch_Array($rs);

PHP 5.2.4-2ubuntu5.9 with Suhosin-Patch 0.9.6.2 (cli) (built: Nov 26 2009 14:00:44)

mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2
TagsNo tags attached.
Attached Filesdiff file icon newembargo_error_fixed_some_innodb_reverted.diff [^] (1,761 bytes) 20-01-10 09:09 [Show Content]

- Relationships

-  Notes
(0050818)
adrian15 (reporter)
20-01-10 09:10

I have attached a patch that reverses the conflictive sentence to its former mysql form.

If there has to be a rewritten to innodb I suppose it should be somewhat compatible with mysql syntax (as it was not here).

I hope that the new innodb implementation (branch) solves these kind of issues.

adrian15
(0050824)
michiel (manager)
20-01-10 14:47

revision 1734

you mean adodb :-) not innodb, but yes, many adodb changes have broken the code, and things like this should get it back in shape. Thanks


Copyright © 2000 - 2017 MantisBT Team
Powered by Mantis Bugtracker