Ottavio Campana wrote:
I need to document the database I develop so that other people can
easily understand how it works.
I particularly want to document the stored procedures. By now I've used
a javadoc style to document them. I can't use tools like doxygen on them
but it is always better tha
On 4/7/06, Ottavio Campana <[EMAIL PROTECTED]> wrote:
> I need to document the database I develop so that other people can
> easily understand how it works.
Another tool to do this is the EMS postgresql manager. It is not a
free tool but it produces absolutely gorgeous html documentation. The
w
Kaloyan Iliev ha scritto:
> Hi,
>
> I am not familiar with doxygen, so I can't give you any advice. To me
> postgresql_autodoc -d works perfectly.
> I am useing version 1.25 of postgresql_autodoc.
>
> I recevice documentation of the sotred rocedures when I have comments on
> them. Then when
>
Hi,
I am not familiar with doxygen, so I can't give you any advice. To me
postgresql_autodoc -d works perfectly.
I am useing version 1.25 of postgresql_autodoc.
I recevice documentation of the sotred rocedures when I have comments on them. Then when
postgresql_autodoc generate HTML documen
Kaloyan Iliev wrote:
> Hi,
>
> I'm using postgresql_autodoc. It is perfect for me. And if you have
> comments in the database the created document is like real documentation:-)
I can't make it work. I'm running Debian etch, and I always get
[EMAIL PROTECTED]:/tmp$ postgresql_autodoc -d tost
Can'
I need to document the database I develop so that other people can
easily understand how it works.
I particularly want to document the stored procedures. By now I've used
a javadoc style to document them. I can't use tools like doxygen on them
but it is always better than nothing.
I'd like to kn
