Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: It makes me go nuts!!!!!!!!

Re: It makes me go nuts!!!!!!!!

From: Ed prochak <ed.prochak_at_magicinterface.com>
Date: 27 Jul 2004 14:24:19 -0700
Message-ID: <4b5394b2.0407271324.719f746f@posting.google.com>


moe_fiddle_at_thegolfcourse.com (moe) wrote in message news:<910a3d79.0407230635.183e15e_at_posting.google.com>...
> >
> > Making it hard on yourself. Why not create do this:
> >
> > CREATE TABLE app_log (
> > output VARCHAR2(4000),
> > outwhen TIMESTAMP DEFAULT SYSTIMESTAMP);
> >
> > Then output into it whatever and whenever you want?
> >
> > Daniel Morgan
>
> That is what I do use. Except for the outwhen column that you
> suggested. I dont need that for the moment.
>
> Still it did not help me find a problem with Intervals. I did not know
> that creating an interval with:
>
> INTERVAL '600' SECONDS; -- (newbie error yes i know: INTERVAL '10'
> MINUTES works).
>
> and then comparing it to an interval generated by two date would yield
> some results that are not really true. Plus the printing of them is
> terrible. Try putting that into your table and you will see 00
> 00:00:00.000000. I think I need a drink and some sleep.
>
> It makes me go nuts i say!!!!!!!!!!!!!

I quess you never programmed in assembler on a machine that has only a serial port and a few LEDs for output devices!

What applies here in PL/SQL, applies in assembler programming and in any other language. And that rule is: use the resources available to you.

A little creativity can go a lot farther than some multicolored realtime WYSIWYG control panel tool.

And there are things you can do to help yourself before you ever begin to execute code like:
* incremental implementation (code one piece at a time) * desk check (manually try to step thru the code simulating the execution)
* code reviews (let someone else read your code and check for errors) * design and design reviews (actually planning your code BEFORE writing it)

Some may express shock at that list. (God forbid we actually documented our design before coding.) All they've ever done is cowboy programming. But there a lot of benefits to doing some real software engineering.

Just my thoughts.

   Ed Received on Tue Jul 27 2004 - 16:24:19 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US