Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Bad Documentation Strikes Again
surely that's emma peel(er) moonlighting as the avengers money dries up...
-- Niall Litchfield Oracle DBA Audit Commission UK ***************************************** Please include version and platform and SQL where applicable It makes life easier and increases the likelihood of a good answer ****************************************** "Howard J. Rogers" <hjr_at_dizwell.com> wrote in message news:14a1f766.0402260937.160127_at_posting.google.com...Received on Mon Mar 01 2004 - 15:00:03 CST
> "Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message
news:<403dcb73$0$7059$ed9e5944_at_reading.news.pipex.net>...
> > blame it on the developer. The docs seem to have been generated from
> > dbmsutil.sql which contains the same clear as mud wording.
> >
> > I do like the version history though
> >
> > Rem tpystyne 10/01/92 - fix Bob's mistakes
>
>
> The funniest one I know of is good old utlexcpt.sql. It's change
> history reads:
>
> Rem epeeler 07/22/91 - add comma
> Rem epeeler 04/30/91 - Creation
>
> It took him 3 months to realise a comma was missing???! And this for a
> create table statement that consists of 4 columns and no constraints!!
>
> Ah, the early nineties. Those were the days, eh?
>
> ;-)
>
> Regards
> HJR