Comment by whynotmaybe
5 days ago
I don't think it's as easy to do the example in the article just by using information_schema.
> Which tables have a column with the name country where that column has more than two different values
But on their product page, the definition of floesql left me puzzled
> It uses intelligent caching and LLVM-based vectorized execution to deliver the query execution speed your business users expect.
> With its powerful query planner, FloeSQL executes queries with lots of joins and complicated SQL syntax without breaking your budget.
INFORMATION_SCHEMA is a good start, but it does not get you to full metadata flexibility. The columns you need just aren't there. It is good to have a standard for the metadata - but the standard isn't ambitious enough (a point I also make in the blog and as you observe, the sample query isn't possible on Information Schema alone)
The Floe engine is a full database on top of Iceberg and Delta storage. The system views are just the tip of the iceberg. We will be blogging more about what we are building.
Good, execution planning for majors DBMS didn't receive any ground breaking evolution because it can be considered a "solved" problem but I'm always curious about new ways to address it.