Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
>
> > Added to TODO:
> >
> > o Have \d show foreign keys that reference a table's primary key
> >
> > http://archives.postgresql.org/pgsql-hackers/2007-04/msg00424.php
>
> We have a patch for this:
>
> http://ar
Bruce Momjian wrote:
> Tom Lane wrote:
> Added to TODO:
>
> o Have \d show foreign keys that reference a table's primary key
>
> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00424.php
We have a patch for this:
http://archives.postgresql.org/pgsql-patches/2008-03/ms
Jim Nasby wrote:
> On Apr 10, 2007, at 9:48 AM, Stephen Frost wrote:
> > Referenced by:
> > "loc_base_clin_loc_base_id_fkey" FOREIGN KEY (loc_base_id) BY
> > wdm_networx.loc_base_clin(loc_base_id)
> > /|
> > \/|\
> >
Tom Lane wrote:
> psql's \d command tells you about outgoing foreign key constraints
> (ie, ones referencing another table from this one). It doesn't tell
> you about incoming ones (ie, ones where another table references this
> one). ISTM it'd be a good idea if it did, as "are there any incoming
On Apr 10, 2007, at 9:48 AM, Stephen Frost wrote:
Referenced by:
"loc_base_clin_loc_base_id_fkey" FOREIGN KEY (loc_base_id) BY
wdm_networx.loc_base_clin(loc_base_id)
/|
\/|\
Referenced column(s) in *this* table
Hi,
On 4/11/07, Guillaume Smet <[EMAIL PROTECTED]> wrote:
On 4/10/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> ISTM it'd be a good idea if it did, as "are there any incoming
> foreign keys" seems to be a question we constantly ask when solving
> update-performance problems, and there isn't any eas
On 4/10/07, Tom Lane <[EMAIL PROTECTED]> wrote:
ISTM it'd be a good idea if it did, as "are there any incoming
foreign keys" seems to be a question we constantly ask when solving
update-performance problems, and there isn't any easy way to check for
such.
Sure. We wrote a stored proc to do that
* Tom Lane ([EMAIL PROTECTED]) wrote:
> one). ISTM it'd be a good idea if it did, as "are there any incoming
> foreign keys" seems to be a question we constantly ask when solving
> update-performance problems, and there isn't any easy way to check for
> such. I'm not real sure what the printout s
psql's \d command tells you about outgoing foreign key constraints
(ie, ones referencing another table from this one). It doesn't tell
you about incoming ones (ie, ones where another table references this
one). ISTM it'd be a good idea if it did, as "are there any incoming
foreign keys" seems to