From: Maarten Scharroo <m.scharroo@elsevier.nl>
Subject: Re: Generating documentation on packages and triggers
Date: 1998/02/02
Message-ID: <34D63D40.314B840C@elsevier.nl>#1/1
Content-Transfer-Encoding: 7bit
References: <34D0AD8D.D80@xpv.xagro.xnl>
Mime-Version: 1.0
To: xfred.xvos@xpv.xagro.xnl
Content-Type: text/plain; charset=us-ascii
Organization: Elsevier Science BV, Amsterdam, The Netherlands
Newsgroups: comp.databases.oracle.tools



Retrofitting isn't the best solution to code the triggers and packages. The
main disadvantage  is the use of free-format style. Use the Module Logic
Navigator to create server code. It offers better formatting and the
possibility of SQL-checking! You can use the declarative approach (
free-format = false ) for all server modules. ( Requires some
experimentation ). Use generate summary
table usages!

The notes-field can be used for extra documentation. There is a repository
report that prints the contents of the notes field.

With regards,

Maarten Scharroo



