Quantcast
Viewing all articles
Browse latest Browse all 295049

Entity query system does not document the NOT BETWEEN operator, but JSON:API supports/uses it

Problem/Motivation

Found in #2491989: [PP-2] PostgreSQL: Use native uuid column type instead of varchar for uuid values

Note: Marking this as a task for the entity system, as my presumption is that JSON:API's usage is fine, we just need to update the documentation. Alternatively this could be seen as a bug in JSON:API if its usage is in fact deemed incorrect.

Per the documentation there is no NOT BETWEEN operator in the entity query system. \Drupal\Core\Entity\Query\QueryAggregateInterface::conditionAggregate() documents BETWEEN but not its inverse.

However, \Drupal\jsonapi\Query\EntityCondition::$allowedOperators does contain NOT BETWEEN, and \Drupal\Tests\jsonapi\Unit\Query\EntityConditionTest does test that it in fact works.

Steps to reproduce

-

Proposed resolution

Either:
Add the NOT BETWEEN operator to the documentation in \Drupal\Core\Entity\Query\QueryAggregateInterface::conditionAggregate().

Or:
Remove support for NOT BETWEEN from JSON:API.

Remaining tasks

User interface changes

-

API changes

Data model changes

Release notes snippet


Viewing all articles
Browse latest Browse all 295049

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>