Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
jordiserra discovered this issue when working with the Search API Ranges module. However, I don't think a patch was ever submitted. So I'm submitting it now.
Comment | File | Size | Author |
---|---|---|---|
#5 | max_inclusive-1363114-5.patch | 660 bytes | emorency |
#4 | max_inclusive-136311-4.patch | 660 bytes | emorency |
query_type_term.inc_.patch | 682 bytes | nbucknor | |
Comments
Comment #1
nbucknor CreditAttribution: nbucknor commentedComment #2
drunken monkeyThanks for submitting the patch!
I don't really know which behaviour could be seen as the „expected“ one, but if no-one objects in the next few days I'm inclined to follow your opinion there.
Comment #3
emorency CreditAttribution: emorency commentedFor SOLR at least, the specification is that it should be a "<="...
See http://wiki.apache.org/solr/SolrQuerySyntax:
"field:[* TO 100] finds all field values less than or equal to 100"
Comment #4
emorency CreditAttribution: emorency commentedThis git patch applies on 7.x.1.x
Comment #5
emorency CreditAttribution: emorency commentedWith the correct file name this time...
Comment #6
Shadlington CreditAttribution: Shadlington commented#5 works for me :D
I too think that should be the default behaviour
warning: contrib/search_api_facetapi/plugins/facetapi/query_type_term.inc has type 100755, expected 100644
Comment #7
mollux CreditAttribution: mollux commentedworks and solves the problem
Comment #8
drunken monkeyThanks, committed!