Jira issue originally created by user lstrojny:
Per default Doctrine 2 adds an IN(...)-part to the query when hydrating an entity where a discriminator column is defined. While this makes sense as a default behavior, it would be pretty helpful if one could disable the WHERE-clause for discriminator columns alltogether for performance optimization.
Comment created by romanb:
That would obviously produce wrong results. Maybe you can elaborate more with an example.
Comment created by lstrojny:
I use ENUM("foo","bar") as discriminator columns. That means, the column will contain the right values out of the box, no further result set limiting required with WHERE.