Bug 51607 - DBDPrepareSQL ( ap_dbd_prepare ) does not work correctly with SQL Statements which has % characters in functions like DATE_FORMAT.
Summary: DBDPrepareSQL ( ap_dbd_prepare ) does not work correctly with SQL Statements ...
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_dbd (show other bugs)
Version: 2.3.12-beta
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2011-08-03 16:18 UTC by Firat Sarlar
Modified: 2018-11-07 21:08 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Firat Sarlar 2011-08-03 16:18:31 UTC
An SQL statemnet like 
"SELECT ID, DATE_FORMAT(  post_date, '%d.%M.%Y %W %H:%i ') AS p_d , post_title, post_content FROM posts;"

With mysql driver.

is not correctly prepared.

This may result of escaping % chars.

Also this bug may be releated to apr_dbd_mysql_driver.
Comment 1 Daniel Gruno 2012-05-01 05:36:46 UTC
From what I can tell, this is simply a matter of internal mechanics using the % sign as an indicator of a variable (%s being most noteworthy). Have you tried using %% instead to denote a percentage sign? Please try so, and if successful, do reply back, so I can perhaps put a note about it in the docs, so we can avoid future bug reports like this.
Comment 2 Firat Sarlar 2012-05-01 14:39:44 UTC
I can not try double % for now - I don't have test env. anymore- but I'm quite sure I have tried many things to avoid errors .
Comment 3 William A. Rowe Jr. 2018-11-07 21:08:52 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.