[DDC-3198] [GH-1075] Fixed query cache id generation: added platform to hash Created: 27/Jun/14  Updated: 27/Jun/14  Resolved: 27/Jun/14

Status: Resolved
Project: Doctrine 2 - ORM
Component/s: None
Affects Version/s: None
Fix Version/s: 2.5
Security Level: All

Type: Bug Priority: Major
Reporter: Doctrine Bot Assignee: Marco Pivetta
Resolution: Fixed Votes: 0
Labels: None


This issue is created automatically through a Github pull request on behalf of vilartoni:

Url: https://github.com/doctrine/doctrine2/pull/1075


There's an issue with the query cache id generation in `Doctrine\ORM\Query::_getQueryCacheId()`.

If you happen to use different connections to different platforms on the same project and you're using the query cache, you will get an exception the moment you try to execute a query which SQL is different depending on the platform and it has been previously cached for the other platform, as they will share the same cache id.

In order to reproduce the bug it is sufficient with using the Doctrine Paginator in a query:

$query = $queryBuilder->setFirstResult(0)

If we run the query for the first time with an empty cache in an Oracle connection and later on we try to run the same query in a MySQL connection, we get the following exception:

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'ROWNUM' in 'where clause'

As it's trying to execute the SQL for Oracle in the MySQL connection due to the same cache id.

This issue can be easily fixed just by taking the platform type into account in the cache id generation.

Comment by Doctrine Bot [ 27/Jun/14 ]

A related Github Pull-Request [GH-1075] was closed:

Comment by Marco Pivetta [ 27/Jun/14 ]

Merged: https://github.com/doctrine/doctrine2/commit/c370426792edda8290843e601e9f95d86a7e873f

Generated at Mon Aug 31 13:53:23 EDT 2015 using JIRA 6.4.10#64025-sha1:5b8b74079161cd76a20ab66dda52747ee6701bd6.