3 ms·

Temp tables are another bandaid. Like views, they are another second-class abstraction intended to address the lack of generality of relations. As you hint, add

Temp tables are another bandaid. Like views, they are another second-class abstraction intended to address the lack of generality of relations. As you hint, adding second-class features is intended to handle pain points while keeping optimization simple, but it's the wrong way to do it IMO. No fixed number of second class features can make up for the lack of relations as first-class values, so this is not just a matter of preference. I actually don't want a general purpose programming language as that's not suitable for data access, I just want a query language that doesn't impose artificial limitations on relations. Edit: although I will admit that programming language theory is a hobby, so that's why I understand the source of the pain every time I have to use SQL. LINQ almost gets this right, but is still a huge improvement on SQL.

ttfkam 3y ago
How would LINQ make jsonpath queries or unroll arrays on the database with unnest?
- naasking 3y ago
  LINQ in EntityFramework (EF) supports querying JSON columns as objects [1]. unnest support is potentially on the horizon for EF core for PG [2], but already supported for Couchbase [3]. [1] https://learn.microsoft.com/en-ca/ef/core/what-is-new/ef-core-7.0/whatsnew#json-columns https://learn.microsoft.com/en-ca/ef/core/what-is-new/ef-cor... [2] https://github.com/npgsql/efcore.pg/issues/1525 https://github.com/npgsql/efcore.pg/issues/1525 [3] https://github.com/couchbaselabs/Linq2Couchbase/blob/master/docs/unnest.md https://github.com/couchbaselabs/Linq2Couchbase/blob/master/...