3 ms·
But I think the ISO paywall prevents adoption in the market you're describing too. I've worked in enterprise and government facing commercial databases for half
by SpicyLemonZest 6y ago
But I think the ISO paywall prevents adoption in the market you're describing too. I've worked in enterprise and government facing commercial databases for half a decade, been involved in dozens of discussions about whether some proposed piece of syntax is standards-compliant, and I haven't once encountered a reference to a section or page number of the actual SQL:2016 ISO standard.
- Hjfrf 6y agoThe only bits people actually know are yyyy-mm-dd and pre-92 implicit joins.
- munk-a 6y agoModern SQL standards seem to be primarily written by the PostgreSQL team - new features they roll out and syntax to describe them tend to be widely adopted. Granted, it could be coming out of ISO itself but nobody would be able to tell since their standards aren't openly published.
- yarcob 6y agoISO standards are often discussed at PostgreSQL conferences, and whenever possible they try to follow the standards. Sometimes standards are written after PostgreSQL implements a feature, and it some cases it seems like they are even written to accomodate PostgreSQL (eg. the SQL/JSON standard seems to take into consideration that a database might have multiple JSON types just like PostgreSQL) But whenever the topic of standards comes up, someone immediately mentions the high price of the standards, and I think only some of the developers actually have a copy of the SQL standards.