Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

getSqlStringForSqlObject() returns an invalid SQL statement with LIMIT and OFFSET clauses #2545

zfbot opened this Issue Sep 28, 2012 · 8 comments


None yet
6 participants

zfbot commented Sep 28, 2012

Jira Information

Original Issue:ZF2-503
Issue Type:Bug
Reporter:Magnus Berglund


The getSqlStringForSqlObject() function returns a SQL statement where the integers for the LIMIT and OFFSET clauses are quoted, which is not correct and MySQL returns an exception.

In the model/mapper

$adapter = $this->getDbAdapter();
$sql = new Sql($adapter);

$select = $sql->select();

$selectString = $sql->getSqlStringForSqlObject($select);

$selectString returns

SELECT `rules_questions`.* FROM `rules_questions` LIMIT '10'

That seems to be an incorrect SQL statement, there should be no quotations around the LIMIT integer

SELECT `rules_questions`.* FROM `rules_questions` LIMIT 10

So when executing the query

$results = $this->getDbAdapter()->query($selectString, $adapter::QUERY_MODE_EXECUTE);

MySQL returns this exception:

SQLSTATE[42000]: Syntax error or access violation: 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 ''10'' at line 1

The same thing happens when adding an OFFSET clause, the integer is incorrectly quoted.

zfbot commented Sep 28, 2012

(Originally posted by: Magnus Berglund on 08/26/12)

An attempt at a fix: zendframework#2244

zfbot commented Sep 28, 2012

(Originally posted by: samsonasik on 09/13/12)

i think ->execute() func can solve this

$statement = $sql->prepareStatementForSqlObject($select);
$result = $statement->execute();

zfbot commented Sep 28, 2012

This issue was ported from the ZF2 Jira Issue Tracker at

Known GitHub users mentioned in the original message or comment:
@ralphschindler, @samsonasik

@ghost ghost assigned ralphschindler Sep 28, 2012

woyteck commented Aug 22, 2013

This bug is still present in stable 2.2.3 as well as dev-master. Why is that?


weierophinney commented Aug 22, 2013

@woyteck If you're still seeing the bug, please provide a reproduce case so we can verify.

woyteck commented Aug 26, 2013

PHP v. 5.4.16
ZF2 v. 2.2.3
MySQL v. 5.5.27

"require": {
"php": ">=5.3.3",
"zendframework/zendframework": "2.2.3"

return array(
'service_manager' => array(
'factories' => array(
'Zend\Db\Adapter\Adapter' => 'Zend\Db\Adapter\AdapterServiceFactory',
'aliases' => array(
'db' => 'Zend\Db\Adapter\Adapter',
'db' => array(
'driver' => 'pdo',
'dsn' => 'mysql:dbname=abc;host=',
'username' => 'abc',
'password' => '123',
'driver_options' => array(

$adapter = $this->getServiceLocator()->get('db');

$select = new Select('test_table');
$select->where(array('type' => 'something'));
$query = $select->getSqlString($adapter->getPlatform());
echo $query;

results in:

SELECT test_table.* FROM test_table WHERE type = 'something' ORDER BY id ASC LIMIT '15'

The same thing happens when I update to dev-master.

fyrye commented Jan 20, 2014

Caused by library/Zend/Db/Sql/Select.php

    if ($driver) {
        $parameterContainer->offsetSet('offset', $offset, ParameterContainer::TYPE_INTEGER);
        return array($driver->formatParameterName('offset'));

    return array($platform->quoteValue($offset)); //<-- just use $offset


    if ($driver) {
        $sql = $driver->formatParameterName('limit');
        $parameterContainer->offsetSet('limit', $limit, ParameterContainer::TYPE_INTEGER);
    } else {
        $sql = $platform->quoteValue($limit); //<-- just use $limit

Bug is still present in Zend Framework 2.2.10. I have to use this version because of running PHP version 5.3.14.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment