You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... then I get a different result! Notice that the correct one uses 5 sql queries vs. the incorrect one uses 2 sql queries.
I don't use owner selectors often, but they are powerful and more efficient, and it's very nice being able to crawl the relationships between pages/repeaters using multiple owner selectors (eg: a.owner.b.owner.c.owner) like I described (something that's undocumented but very powerful).
However as mentioned, it seems the order in which you define the pieces of the selector matters. Is this a bug? If not, is there documentation stating how the order of the pieces of a selector are supposed to influence the resulting sql queries?
Note: Using PW 3.0.247
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
I have the following structure on my site:
Another way to say the above would be like this:
Now let's say I want to get all of the payloads where the order is not a "test" with some other things. I would do this:
The above selector gives the correct results.
However if I swapped the positions of "1 owner" and "3 owners" like this:
... then I get a different result! Notice that the correct one uses 5 sql queries vs. the incorrect one uses 2 sql queries.
I don't use owner selectors often, but they are powerful and more efficient, and it's very nice being able to crawl the relationships between pages/repeaters using multiple owner selectors (eg: a.owner.b.owner.c.owner) like I described (something that's undocumented but very powerful).
However as mentioned, it seems the order in which you define the pieces of the selector matters. Is this a bug? If not, is there documentation stating how the order of the pieces of a selector are supposed to influence the resulting sql queries?
Note: Using PW 3.0.247
The text was updated successfully, but these errors were encountered: