51
SQL Has Problems. We Can Fix Them: Pipe Syntax In SQL
(research.google)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Aug 2024
51 points (90.5% liked)
Programming
17314 readers
33 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
I lile this a lot. This reminds me a lot of KQL (a microsoft query language that's used for a bunch if azure logging).
I use a lot of python pandas/dask- I've definitely got used to viewing a table as a series of operations to perform rather than the kind of declarative queries you get in SQL.
At what point is it no longer SQL? If we're changing fundamental stuff, I'd love a way of writing loops or if statements that isn't painful too.
Stored Procedures have been a thing for literally decades. But they're an absolute pain.
What would really improve the usefulness of databases are autoindexes and generally more "let me handle that for you". I'd argue 90% of business apps essentially need a way to store objects and their relationships, but doing that in an efficient manner is really hard (at least if you've got a few more rows to handle).
SQL has pretty powerful conditional support support already and lateral joins are essentially loops if you're unfamiliar with them.