some of “pass in” is ambiguous here. As I understand it…. 1. the users hands a query to sqlite 2. sqlite hands it to a virtual table 3. the virtual table does what it will using the context and constraints and returns data to sqlite 4. sqlite does various filtering and joining Because it’s passing back through sqlite, if you have something like

packets_to_capture = "10"

set in a where clause, then sqlite will require those rows to match against it. And you’ll need to return that in the data. I think

hidden

makes a lot of sense there too. As when you say

select *

you probably don’t need to see the options echoed back