4 ms·
I am a rather seasoned database person at this point, but when I wasn't - when I was just getting into database interactions - I had an academic background in r
by munk-a 6y ago
I am a rather seasoned database person at this point, but when I wasn't - when I was just getting into database interactions - I had an academic background in relational algebra and I knew that SQL was the main communication language. For day to day work this was fine but at one point I was tasked with making our application DBMS neutral with support for running on top of SQLServer (TSQL), PostgreSQL, and MySQL. My first thought when coming to this problem was, well, let's take a good look at the grand daddy doco so I attempted to find the SQL standard.
It disappoints me that, to this day, the best reference for pure SQL out there are the postgres docs, postgres is actually pretty good about calling out non-compliances so you can get a really good grounding of what code is likely to be cross platform compatible.
I 100% agree with Tim Sweeney's sentiment. ISO are terrible at their job.
- deleted 6y ago[deleted]
- aesyondu 6y agoI was curious where the actual SQL standard document is. With a quick search this is the best I can come up with: Second informal review draft from the accepted answer: http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt Downloadable iso standards (C-f sql) http://www.iso.org/PubliclyAvailableStandards http://www.iso.org/PubliclyAvailableStandards https://stackoverflow.com/questions/1714461/ansi-sql-manual https://stackoverflow.com/questions/1714461/ansi-sql-manual