pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: pgsql-docs@postgreSQL.org
Subject: Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS
Date: Sun, 05 Sep 2010 22:16:57 -0400
Message-ID: <5762.1283739417@sss.pgh.pa.us> (raw)
In-Reply-To: <1283712463.12666.7.camel@vanquo.pezone.net>
References: <alpine.DEB.2.00.1008311337530.2449@localhost.localdomain>
	<2683.1283266019@sss.pgh.pa.us>
	<alpine.DEB.2.00.1009011557480.2570@localhost.localdomain>
	<1283369900.15386.0.camel@vanquo.pezone.net>
	<alpine.DEB.2.00.1009020741380.2656@localhost.localdomain>
	<1283438419.23199.0.camel@vanquo.pezone.net>
	<alpine.DEB.2.00.1009021959070.2656@localhost.localdomain>
	<6462.1283454730@sss.pgh.pa.us>
	<alpine.DEB.2.00.1009031348321.2448@localhost.localdomain>
	<22801.1283525905@sss.pgh.pa.us>
	<alpine.DEB.2.00.1009031920460.2622@localhost.localdomain>
	<1283535870-sup-2648@alvh.no-ip.org>
	<26284.1283536406@sss.pgh.pa.us>
	<1283712463.12666.7.camel@vanquo.pezone.net>

[ redirecting to pgsql-docs ]

Peter Eisentraut <peter_e@gmx.net> writes:
> On fre, 2010-09-03 at 13:53 -0400, Tom Lane wrote:
>> It would probably be reasonable to put something into chapter 34 of the
>> docs pointing out this limitation.  I'm not sure exactly where though.
>> Should we invent a "compatibility issues" section in that chapter,
>> analogous to the ones we have for individual SQL commands?  Are there
>> other issues worth documenting for the information_schema views?

> A very similar issue is already documented here:
> http://developer.postgresql.org/pgdocs/postgres/infoschema-triggers.html

That sort of annotation was my first thought, but we'd have to repeat
ourselves in multiple places because there are several views that are
affected by the constraint-name issue.  (Come to think of it, isn't
triggered_update_columns also affected by the trigger-name issue?)

Is that the direction we want to go, or would it be better to factor
the information out into a separate page about compatibility gotchas?

			regards, tom lane



view thread (33+ messages)  latest in thread

Message-ID: <5762.1283739417@sss.pgh.pa.us>
Permalink:  ../5762.1283739417@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/5762.1283739417@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, peter_e@gmx.net, alvherre@commandprompt.com, coelho@cri.ensmp.fr
  Subject: Re: [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS
  In-Reply-To: <5762.1283739417@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox