Hacker News Reader

Their examples showing why Trilogy is so good are comparing it against poorly written SQL with poorly designed schemas. It reduces my confidence that their tool is actually solving real problems but instead was borne out of frustration in learning SQL and databases.

View on HN

Any particular examples you have in mind? The demo is just referencing https://github.com/duckdb/duckdb/tree/main/extension/tpcds/d... which I wouldn't regard as a standard of good SQL; (implicit joins, yikes!) - but is a useful capability reference (as is tpc-ds in general).

As I tried to convey, I like SQL a lot - my frustration is more around the lifecycle and maintainability.

Happy to add more ergonomic references in other places, if you have some good examples to reference against?

Reply on news.ycombinator.com