Fred van Engen wrote: > On Fri, Aug 22, 2003 at 01:16:48AM -0500, Hans van Harten wrote: >> that comes with neither warnings nor errors reported ... > Error reports would have been nice, but why does your application > supply these incorrect dates anyway? Probably because some user typed > them. And what are you going to tell the user when you get a generic > MySQL error for an INSERT with many values? > 'Oops, something went wrong'? Planned to dump it into MySQL and check only if MySQL croaked about it.
> Just check the values in your application, like you should do for any > value coming from an external source. Then you can tell the user > exactly what went wrong for each field. It also prevents garbage or > badly formatted data from entering your database. My checks might not match those of (the next version of) MySQL and at that time the difference in thoughts will pass unnoticed ! HansH -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
