Closed lostmygithubaccount closed 1 year ago
I understand the motivation for the example, but it's quite long.
The long example is fine, but for the future would you mind showing a separate code block that contains only the failure? It's hard to see what's happening because of all the setup code.
Also you don't need to keep strip().strip(";")
-ing. Are you seeing failures when you don't do that?
Another thing that would help cut the example down is making some variables of the expressions instead of duplicating them only to show their sql.
Sorry, I keep noticing things 😄
missions
is unused, which adds noise to understanding the problem
Hm, there's a final outer projection, which will erase the ORDER BY
.
It seems to only show up in the trino backend curiously enough: there's no outer projection generated for the duckdb backend.
Ok, it's not really a duckdb vs trino vs other issue, we're generating an extra project for all sqlalchemy backends. It just happens to be the case that DuckDB will presents the results in the same order every time, but it's definitely not something we should depend on.
What happened?
this is with the Trino backend connected to a demo Starburst Galaxy account using the sample dataset they provide, it should be relatively easily reproducible. in summary for some reason passing in SQL to
.sql()
doesn't work as expected; the equivalent Ibis is fine; the SQL versions aren't ordered as expectedWhat version of ibis are you using?
master
What backend(s) are you using, if any?
trino
Relevant log output
Code of Conduct