>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3376606. --> Reported by: [mcdruid](https://www.drupal.org/user/255969) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Running entitycache's test suite with sqlite reveals that the following two taxonomy tests fail:</p> <pre>testTaxonomyGetTermByName<br><br>fail: [Other] Line 981 of modules/taxonomy/taxonomy.test:<br>Term loaded with uppercased name.<br><br>fail: [Other] Line 985 of modules/taxonomy/taxonomy.test:<br>Term loaded with lowercased name.</pre><p>As far as I can see this is because when core runs <code>taxonomy_get_term_by_name()</code> without entitycache, <code>DrupalDefaultEntityController::load</code> does this:</p> <pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Build the query.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $query = $this-&gt;buildQuery($ids, $conditions, $revision_id);</pre><p>...which produces a select query with a condition along the lines of <code>base.name LIKE "foo"</code>.</p> <p>Whereas with entitycache enabled, <code>\EntityCacheControllerHelper::entityCacheLoad</code> does this:</p> <pre>&nbsp;&nbsp;&nbsp; if ($conditions) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $query = new EntityFieldQuery();<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $query-&gt;entityCondition('entity_type', $controller-&gt;entityType);<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; foreach ($conditions as $property_name =&gt; $condition) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Note $condition might be multiple values, which are treated as OR<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // by default.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $query-&gt;propertyCondition($property_name, $condition);</pre><p>...where <code>EntityFieldQuery::propertyCondition</code> uses a default operator of <code>=</code> for the condition.</p> <p>With MySQL this typically makes no difference, but with other database systems which are case sensitive by default, there's a difference in behaviour as a result of the different operators / SQL syntax.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>Run entitycache tests with sqlite (and probably postgres) e.g.:</p> <pre>---- EntityCacheTaxonomyTermTestCase ----<br><br><br>Status&nbsp;&nbsp;&nbsp; Group&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Line Function&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>--------------------------------------------------------------------------------<br>Fail&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Other&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; taxonomy.test&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 981 TaxonomyTermTestCase-&gt;testTaxonomyG<br>&nbsp;&nbsp;&nbsp; Term loaded with uppercased name.<br>Fail&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Other&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; taxonomy.test&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 985 TaxonomyTermTestCase-&gt;testTaxonomyG<br>&nbsp;&nbsp;&nbsp; Term loaded with lowercased name.</pre><h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>I suppose to fix this we'd need to do something like explicitly pass an appropriate operator to <code>EntityFieldQuery::propertyCondition</code> for certain conditions.</p> <p>For example, this quick hack makes the tests pass:</p> <pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; foreach ($conditions as $property_name =&gt; $condition) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // Note $condition might be multiple values, which are treated as OR<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // by default.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $operator = NULL;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if ($property_name == 'name') {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $operator = 'LIKE';<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $query-&gt;propertyCondition($property_name, $condition, $operator);<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</pre><p>However, we'd need to do something like actually look up the property name in the base table's schema to determine whether it's appropriate to set the operator to something other than the default.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Outlined above.</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>n/a</p> <h3 id="summary-api-changes">API changes</h3> <p>n/a</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>n/a</p>