also how does it do with transitive joins across multiple tables that may not have FK/PK relationships? Other key features that would put this over the top: Usage analysis and query rewriting for inefficient already existing queries.
For the joins, we give the right context so that the model can infer the relationships: the schema of each table + how the joins are already done in your repository/query history.
Usage analysis is definitely on the roadmap: we want to access the logs of the data warehouse to mesure usage of each table.