2 ms·
If only this was the case. Except that every database has their own flavour of SQL with plenty of proprietary extensions. Not to mention each database will supp
by threeseed 11y ago
If only this was the case. Except that every database has their own flavour of SQL with plenty of proprietary extensions. Not to mention each database will support a different subset of SQL.
- dragonwriter 11y ago> Except that every database has their own flavour of SQL with plenty of proprietary extensions. Not to mention each database will support a different subset of SQL. Its a lot easier to become familiar with a new SQL dialect than a new query language, especially since a lot of basic querying will be the same between different dialects.
- threeseed 11y agoLearning the basics is easy with any query language eg. MongoDB/ES JSON. It's when you start writing more advanced queries that you realise that SQLs "write once, run anywhere" premise is an illusion.
- hobs 11y agoDont know why anyone is downvoting this, this is absolutely true, and its even worse because the subset might work differently with the same keywords due to the underlying optimizer differences. This makes code you wrote in two different engines with the same syntax run vastly differently. Only if you are writing basic queries is the ansi sql promise realized.
- carterehsmith 11y ago>>Except that every database has their own flavour of SQL Sure, but simple queries, like the poster above provides as an example, have been standardized for like decades, and work the same across pretty much every credible RDBMS. https://news.ycombinator.com/item?id=10577996 https://news.ycombinator.com/item?id=10577996
- collyw 11y agoSure, but its relatively easy traslating from one dialect of SQL to another, as opposed to learning a whoe new query language.