Fixed query cache id generation: added platform to hash

[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)
    ->setMaxResults(50)
    ->getQuery()
    ->getResult();

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.

[doctrinebot]

Hello,

thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:

http://www.doctrine-project.org/jira/browse/DDC-3198

We use Jira to track the state of pull requests and the versions they got
included in.

[Ocramius]

@vilartoni are you using the same cache across different connections on purpose?

[vilartoni]

@Ocramius Yes. We're using a common cache server for all cached queries.

[Ocramius]

Can you check if the travis failure here is related to your change?

[vilartoni]

Sure. I'd say it is not. It's something to do with the MOD() dql function failing in postgresql.

[Ocramius]

restarted that worker

[vilartoni]

All green.

[Ocramius]

Could you add it as a new line and use &platform=? Looking good otherwise.