Subfield selector unexpectedly returns result in OR like fashion

[ruudalberts]

The selector "template=accommodationtype,availability.column=1194,availability.row=1889,availability.value=1"
should return all accommodationtypes where all availability restrictions match: availablity.column = 1194 AND availability.row=1887 AND availability.value=1

What actually happends (looking at the querylog), is that the availability field is joined 3 times, matching all 3 subfields seperately, then grouping the result and thus returning all accommodationtypes where either of the restrictions are met:

More info and a proposed fix here: https://processwire.com/talk/topic/11099-subfield-selector-unexpectedly-returning-result-in-or-like-fashion/

[ryancramerdesign]

What type of field is "availability"? (Page field?). Are any of your subfields: "column", "row", or "value" able to contain multiple values? For instance, might they be Page fields or Options fields?

[ryancramerdesign]

I'm wondering if you might be looking for the @field.subfield grouping that we introduced in PW 2.5? See here: https://processwire.com/blog/posts/processwire-2.5-changelog/#selectors-and-finding-pages

[ruudalberts]

Hi Ryan,

I already added a comment on this in the forumtopic: https://processwire.com/talk/topic/11099-subfield-selector-unexpectedly-returning-result-in-or-like-fashion/?p=104303

Do your prefer to keep the conversation on the forums, or here on github?