Re: Invalid Date Bug

["Peter Grigor" <suppressed>]

I'm with you for sure...client processing is the way to go...fat servers
suck.

Peter
<^_^>
---------------------------------------------
Peter Grigor
Hoobly Free Classifieds
http://www.hoobly.com


----- Original Message -----
From: "Paul DuBois" <suppressed>
To: "Peter Grigor" <suppressed>; "Don Vu"
<suppressed>; "MySQL Mailing List (E-mail)"
<suppressed>
Sent: Friday, February 14, 2003 4:59 PM
Subject: Re: Invalid Date Bug


> At 16:55 -0500 2/14/03, Peter Grigor wrote:
> >Yep, you're right. Never noticed that before :)
> >
> >I think that would probably be considered a bug. But possibly for
> >efficiency's sake the check was made ultra simple.
>
> It can be argued either way.  You could just as well consider it a
> bug that you try to shove garbage into your database. :-)
>
> Client-side validation has the disadvantage that you must do it in
> each client, of course.  On the other hand, for things like web apps,
> you may as well validate the data in the client anyway: Suppose MySQL
> validated the date and returned an error for a bad data.  You'd just
> have to tell the user that anyway, plus you wasted time sending a
> bad query to the server.  If you check the date in your app, you can
> tell the user immediately and skip the bad query.
>
> >
> >Peter
> ><^_^>
> >---------------------------------------------
> >Peter Grigor
> >Hoobly Free Classifieds
> >http://www.hoobly.com
>
>


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <suppressed>
To unsubscribe, e-mail <suppressed>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php