<@U7QP20JQH>The per row table call in a JOIN or th...
# cores
Stefano Bonicatti
10/06/2023, 7:07 PM@sephThe per row table call in a JOIN or the single constraint passed to the table per IN constraint, has always been the case since I remember. Although I know that we have functions to get multiple constraints per generate call, I never have seen them actually get more than 1.
Stefano Bonicatti
10/06/2023, 7:08 PMBut in a JOIN it's expected, because you're expected to use a primary key which will yield a single row each time
s
seph
10/06/2023, 7:08 PM
I agree they’ve been issues for a long time.
s
Stefano Bonicatti
10/06/2023, 7:08 PMthough obviously the difference here is that table querying is more involved than just a query to a table in a physical DB
s
seph
10/06/2023, 7:09 PM
Ages ago I remember asking Teddy about it, and he was sure generate was only called once.
seph
10/06/2023, 7:09 PM
And I feel like Alex used to poke around this part of the code
seph
10/07/2023, 12:08 AM
I found the old bug report — https://github.com/osquery/osquery/issues/5379