Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of vilartoni:
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 created by @doctrinebot:
A related Github Pull-Request [GH-1075] was closed:
Comment created by @ocramius:
Issue was closed with resolution "Fixed"