I'll do some tests - one limitation i noticed is one can only document objects from the connection's schema; it would be nice to be able to extend the selection as for the "export db" feature
maybe you're using the wrong tool - have you seen what the modeler can generate for db documentation?
the schema doc is designed for a single schema in mind
> maybe you're using the wrong tool - have you seen what the modeler can generate for db documentation?
alright, how should i go about it ?
i am basically interested in generating the pldoc for a bunch of hand-picked packages (using a connection that can browse everything)
I tried importing a single package and could not figure out how to generate the db doc from the resulting model
> the schema doc is designed for a single schema in mind
was it always that way ? i seem to recall having to wait forever while it generated html for a whole db (probably still in 3.x)
>>could not figure out how to generate the db doc from the resulting model
there are various reporting options available, which one did you try?
it doesn't support the PL/Doc feature
Two little glitches I noticed:
when hitting <Ctrl><Space> above a procedure specification, sqldeveloper generates a comment skeleton which is very helpful, yet
- @param (and @return) annotations are injected in upper-case, whereas the help generator expects lower-case (and chokes on upper-case). Maybe this is influenced by a preference being set for upper-case SQL keywords but it shouldn't
- the generated block comment does not start every line with a star, which causes problems when deploying a package through sql*plus (which looks for param.sql and return.sql)
in other words we get the following
@PARAM p_some_parameter VARCHAR2
while this would be better
* @param p_some_parameter VARCHAR2
It also seems that when a parameter is documented with several lines, sometimes they are retained and sometimes only the first one is kept in the generated html.