MIME-Version: 1.0
In-Reply-To: <20171221031511.GX4628@tamriel.snowman.net>
References: <20171220090816.25744.72592@wrigleys.postgresql.org>
 <CAB7nPqRgrAuqT-xeEZqtmaT7SToKQrE3Vd+yxigd0xtiy88x9Q@mail.gmail.com>
 <20171221031511.GX4628@tamriel.snowman.net>
From: Michael Paquier <michael.paquier@gmail.com>
Date: Thu, 21 Dec 2017 12:29:12 +0900
Message-ID: 
 <CAB7nPqTagNTV5LbKz3Jekrd2DkxoaER+7sPKPSmjkd-aY1foeQ@mail.gmail.com>
Subject: Re: Missing column_constraint explanation
To: Stephen Frost <sfrost@snowman.net>
Cc: lampacz@gmail.com, pgsql-docs@postgresql.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Dec 21, 2017 at 12:15 PM, Stephen Frost <sfrost@snowman.net> wrote:
> Now, if we could do that in such a way that we avoid having to actually
> duplicate the 'source' for these productions into different places in
> the documentation, that would be fantastic because it certainly isn't
> fun having to find all the places that need to be updated, but I'm not
> sure how easy that would be to do (and to make work with how psql's help
> is generated...).

You are looking for something like how feature-supported.sgml is
handled after its automatic generation, except that in this case you
just create a new sgml file which has the definition data you want to
load, define it with <!ENTITY blah SYSTEM "blah.sgml">, and then load
it using something like an entity &blah; in the CREATE or ALTER TABLE
docs. That's a bit of refactoring though, but you could shape it by
putting all those lower-level definitions in a subdirectory like
sgml/defs or such, avoiding any duplication in those definitions.
-- 
Michael