| From: | SQLpro <sqlpro(at)sqlspot(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Primary key error in INFORMATION_SCHEMA views |
| Date: | 2018-05-24 08:01:09 |
| Message-ID: | 1527148869517-0.post@n3.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi Tom,
For a DBMS which loudly proclaims to be the most respectful of the SQL
standard, not being able to use the INFORMATION_SCHEMA views because of such
an error seems to me to go against its philosophy.
Can not you change that by adding a configuration parameter, for a future
version, that would allow you to apply these views more strictly?
More pragmatically, what good can these views serve if we can not use them
properly without bug? Better to remove them if you choose not to fix this
bug …
A +
-----
Frédéric BROUARD - Data Architect - Paris / PACA, France - SARL SQL SPOT
Teacher : CNAM PACA, ISEN Toulon, CESI/EXIA Aix en Provence, EPITA Paris
Expert on SQL and Relational DBMS : Microsoft SQL Server / PostGreSQL...
My French site about SQL language and RDBMS http://sqlpro.developpez.com
The books I wrote : https://www.amazon.fr/Frédéric-Brouard/e/B004MQ3NVQ
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2018-05-24 12:28:03 | Primary key error in INFORMATION_SCHEMA views |
| Previous Message | Anjul Tyagi | 2018-05-24 07:58:43 | Re: PGADMIN4 V3.0 Error |