From: | Rémi Cura <remi(dot)cura(at)gmail(dot)com> |
---|---|
To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Autodocumenting plpgsql function |
Date: | 2013-11-26 12:13:16 |
Message-ID: | CAJvUf_vA6Zt9_tZXiYC=jtrVcFRmDZ+GRtTMoW3ULZpTStxJRw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hey thanks for the answer.
I'm thinking way more than that.
Typically in you comments you include special tags, like @input, then
doxygen will parse it and generate an html documentation.
Cheers,
Rémi-C
2013/11/26 Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
> Rémi Cura wrote:
> > somebody knows of a way to autodocument plpgsql function, in a docxygen
> style
> > (adding tags in comments for instance, or creating doc templates to
> fill).
> >
> > It would really help to write the doc and maintain it.
>
> I am not sure what you need, but I see two ways to
> document a function:
>
> 1) With /** .. */ comments in the beginning.
> Maybe doxygen can be used to parse a database dump.
>
> 2) With COMMENT ON FUNCTION ... IS '...';
> That also keeps the documentation close to where
> the code is, and it shows up in database dumps.
>
> Yours,
> Laurenz Albe
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Kroon | 2013-11-26 13:02:15 | xmlagg doesn't honor LIMIT? |
Previous Message | Karsten Hilbert | 2013-11-26 11:25:32 | a PostgreSQL slogan misused |