risingwavelabs / risingwave

Best-in-class stream processing, analytics, and management. Perform continuous analytics, or build event-driven applications, real-time ETL pipelines, and feature stores in minutes. Unified streaming and batch. PostgreSQL compatible.
https://go.risingwave.com/slack
Apache License 2.0
6.82k stars 567 forks source link

Discussion: "Even Friendlier SQL with Risingwave" #15637

Open lmatz opened 6 months ago

lmatz commented 6 months ago

A lot of user-friendly and innovative ideas from Even Friendlier SQL with DuckDB But maybe not all of them are suitable for RW, let's have a discussion.

Welcome leave comments (pro/con) for the syntax and give it a 👍 or 👎

lmatz commented 6 months ago
lmatz commented 6 months ago
lmatz commented 6 months ago
lmatz commented 6 months ago
lmatz commented 6 months ago
lmatz commented 6 months ago
lmatz commented 6 months ago

The SQL 92 standard uses CORRESPONDING instead of BY NAME https://github.com/risingwavelabs/risingwave/issues/17451#issuecomment-2191639814

lmatz commented 6 months ago
lmatz commented 6 months ago
lmatz commented 6 months ago

Supported by #11937. Beware of the complications it troduced: https://github.com/risingwavelabs/risingwave/pull/11937#discussion_r1309719284 #13724

lmatz commented 6 months ago
lmatz commented 6 months ago

See #10847 and https://github.com/risingwavelabs/risingwave/issues/6934#issuecomment-1396344815

lmatz commented 6 months ago

Also part of PostgreSQL. See the same 2 issues linked under Exploding struct.*

lmatz commented 6 months ago
github-actions[bot] commented 3 months ago

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.