efromvt

8 ms·

121.
by efromvt 2y ago
Also full agreement! In an optimistic view, the SQL layer (at a slightly higher level) unifies the top level accessibility tools (NLP, drag/drop chart result builders, etc) with the more tech-familiar level of analysts/engineers,
122.
by efromvt 2y ago
Had some more time to drill into this and we've ended up with a very similar approach to a lot of the metadata definition and resolution - I'd love to chat sometime about how you've solved some of the common problems (table s
123.
by efromvt 2y ago
More effort has definitely been focused on the 'select' aspect, since you often select more than you mutate - and even in the future state, for data warehousing cases updates can be relatively rare. I definitely don't see it
124.
by efromvt 2y ago
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; (i
125.
by efromvt 2y ago
Thanks on the name, hah. Been fun to see the progress PRQL has made going mainstream!
126.
by efromvt 2y ago
Oh wow yeah, a lot of parallels - thanks for sharing, I'll take a deeper dive in a bit. I think there's a lot of demand and a lot of space for different solutions; Trilogy definitely aspires to hew closer to standard SQL. (I actua
127.
by efromvt 2y ago
Here's an example of what this would look like in practice; https://gist.github.com/greenmtnboy/580f479c80e23c5362a70b43...
128.
by efromvt 2y ago
To expand on previous answer, right now this would be represented as: key firstname string; key lastname string; auto full_name <- concat(firstname, ' ', lastname); datasource people ( firstname:firstname, lastname:lastname ) a
129.
by efromvt 2y ago
Hmm - in Trilogy, if both tables had firstname and lastname as concepts bound to them, and you created full name that was the concat of those concepts, you'd only need to define fullname once and the calculation would work against both
130.
Show HN: Trilogy – A Reusable, Composable SQL Experiment(trilogydata.dev)
78 points by efromvt 2y ago|40 comments
131.
by efromvt 2y ago
The USG solution is just Google Analytics though, so…
132.
by efromvt 2y ago
Updated the section on query resolution to be more explicit about datasources + join inference - thank you for the feedback, and let me know if that helps! I'll try to get a more detailed section on that further on to really dig into i
133.
by efromvt 2y ago
Datasource bindings are explicit, then the resolution to datasources at query time is automatic/consistent for a given query set and semantic model. If you have only one [non-partial] datasource with a column bound for a concept, that
134.
by efromvt 2y ago
Ah - so you don't ever express a join in the language - they're completely abstracted away from the user and resolved at runtime based on the bound tables in the semantic model. The 'hello world' and demo examples with m
135.
Show HN: PreQL/Trilogy – A Higher-Level, Composable SQL(github.com)
3 points by efromvt 2y ago|5 comments