3 ms·

> Did we all forget how and why SQL standards were created in the first place? How customers were demanding a certain level or interoperability? Do we think we

> Did we all forget how and why SQL standards were created in the first place? How customers were demanding a certain level or interoperability? Do we think we don't need that anymore and the past reasons aren't there? So, since you wrote here originally in part to complain about the low bar PostgreSQL set for themselves in trying to be standards compliant to an old standard (which has now been shown to merely be due to a stale document)... just who, in your view, should the good folks on the PostgreSQL dev team look to for how it's done? Which RDBMS provider/vendor has set the bar high for themselves in regard to standards compliance and achieved it?

avmich 9y ago
I'm not particularly familiar with how PostgreSQL development is done. I suspect it carries a lot of baggage from the past releases, both good and bad. I hope the team will see the value in structuring the product in such a way that users of the product won't feel themselves making a hard choice taking PostgreSQL for new projects - or maintaining it in existing systems. > Which RDBMS provider/vendor has set the bar high for themselves in regard to standards compliance and achieved it? I think we had better compliance to the standards in DB industry as a whole some years ago, but that's just a feeling. I think we have right now better compliance to the standards - as in industry mostly following standards within, say, 5 years - in branches of engineering like compilers and browsers. In open source SQL engines PostgreSQL is overall one of the strongest propositions which I recommend often. However you don't maintain your lead if you don't recognize your weak points.