in reply to Re: Re: Re: Date conversion with Class::DBI
in thread Date conversion with Class::DBI

And what does allowing two digit years (you mentioned you wanted to allow this), and odd date formats imply? Well its a threat to the structural integrity of the data.

Actually, I was thinking more along the "be liberal in what you accept from others" vein. This doesn't have to conflict with data integrity.

Also, I can't bring myself to code defensively against law suits.

  • Comment on Re: Re: Re: Re: Date conversion with Class::DBI

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Date conversion with Class::DBI
by demerphq (Chancellor) on Jul 08, 2003 at 10:38 UTC

    Accepting 2 digit years does conflict with data integrity. There are at least three commonly used interpretations of 01/02/03 (is it 2001-02-03 => YY/MM/DD or 2003-02-01 => DD/MM/YY or 2003-01-02 => MM/DD/YY ?) (And when you include uncommon formats it gets worse.) Being liberal in what you tolerate doesnt mean you have to tolerate totally ambiguous input.

    Beside the lawsuits Id be thinking of all the hassle of cleaning up the data when you get an American in the office (or any nationality NOT the one you are designing for.)

    Anyway, i'll let it rest now, and hope you realize I said all of this in the best of intentions. :-)

    Regards,


    ---
    demerphq

    <Elian> And I do take a kind of perverse pleasure in having an OO assembly language...