The problem with this approach is dblink[1], for example, in which I can't use
reference (as I've already used for dblink itself). I will probably have to
use in theses cases then...
[1] http://www.nan-tic.com/ftp/pgdoc/dblink.html
A Dijous 11 Octubre 2007, Tom Lane va escriure:
> Guillaume Le
Am Mittwoch, 10. Oktober 2007 schrieb Albert Cervera i Areny:
> - I can't make this "contrib" doc a part because Reference already
> is a part and can't be nested.
The Reference things in DocBook are mostly to support legacy man pages, and
man pages are not necessary the greatest format t
Hi
attached some minor corrections, mainly completion of removal of
the "relation with OID # does not exist" item, and some URL corrections.
Ian Barwick
Index: FAQ.html
===
RCS file: /projects/cvsroot/pgsql/doc/src/FAQ/FAQ.html
Not that I want to make each module a reference. With previous discussions we
seemed to agree that:
- It should go into the References part of the documentation (right
after "III. PostgreSQL Server Applications).
- Each module docs should be in a single page, mainly because some contrib
modules
Patch applied. Thanks.
---
Ian Barwick wrote:
> Hi
>
> attached some minor corrections, mainly completion of removal of
> the "relation with OID # does not exist" item, and some URL corrections.
>
> Ian Barwick
[
