Replies: 1 comment 2 replies
-
The results should behave as you'd expect ... run the query, order the result, then limit it to the first 5. Behind the scenes, the plugin foreign data wrapper actually executes the query and returns the full set of table results to postgres. Postgres then does the order by and limit in it's own space. (FYI, this is why the cache is still used even if you change the order by.) Questions:
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've tried queries against the aws api gateway tables, ordering by name, with LIMIT. They seem to omit many entries. This is not what I would expect.
For example, with this query:
I get back this result, starting with apis whose names begin with "D*":
Contrast to the console, where there are many entries before we get to apis whose names begin with "D*":
Any idea about the explanation for this? I've tried looking for the underlying GO api call parameters in the INFO debug log in ~/.steampipe/logs, but there's not much helpful there.
Is it expected that the
order by
is applied after some subset of results is first returned withLIMIT
? I would expect theorder by
to be applied first?Beta Was this translation helpful? Give feedback.
All reactions