From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Clarification to catalog-pg-class |
Date: | 2009-02-12 03:17:12 |
Message-ID: | 200902120317.n1C3HCO16080@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > Josh Berkus wrote:
> >> Bruce,
> >>
> >>>> Currently, catalog-pg-class is a bit confusing as to where FKs are
> >>>> tracked in pg_class. Please update the lines for relchecks and
> >>>> reltriggers to read:
> >>>>
> >>>> relchecks int2 Number of check constraints on the table (but not
> >>>> other types of constraints); see pg_constraint catalog
> >>> Uh, why do we have to say "but" when we clearly say "check constraints"?
> >>> Do we need to say "CHECK" contraints?
> >> Because I've encountered two people on IRC (and a client) who were
> >> confused about this, and it confused me briefly when I fielded their
> >> questions. Saying "CHECK constraints" would also probably do it, or
> >> saying "check constraints (only)"
> >
> > Uppercase done, with <literal> tag.
>
> This is inconsistent with the rest of the documentation.
Should I use <emphasis>? <literal>?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2009-02-13 09:13:42 | Re: Clarification to catalog-pg-class |
Previous Message | Peter Eisentraut | 2009-02-11 09:23:30 | Re: Clarification to catalog-pg-class |