On Feb 28, 3:09 pm, "Luch" <DarthL..._at_gmail.com> wrote:
> On Feb 28, 2:28 pm, Brian Peasland <d..._at_nospam.peasland.net> wrote:
>
>
>
> > Since this is in development, does it really matter if their activity is
> > "off"? They aren't working on real data anyway.
>
> Yes, it does... What I mean is that the developer uses SYSDate, and
> doesn't notice any problem. When our program is deployed to customers,
> the sysdate function call is still there (instead of the one he
> should've been using) and the customer sees the error. Of course the
> real solution is the programmer should be calling our own function to
> return the current datetime instead of using sysdate. I want to block
> them from using sysdate.
Then it is a management/process issue. Do code reviews, inspections,
walkthrus, or whatever process you prefer. This problem could be
solved by a simple grep of the source code for sysdate. Why code a
workaround for a development process problem?
Received on Thu Mar 01 2007 - 12:34:42 CST
