Fabien COELHO wrote:
>
> >> 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?
> >
> > It would probably be better to explain globally applicable issues in a
> > separate section.
>
> I agree that a general caveat is better, together with a one line
> reference in the documentation of each table with an issue.
Oh, I just noticed this. Can you give me a list of information_schema
tables that have this issue? I am only aware of
referential_constraints.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
