> -----Original Message----- > From: David Griffiths [mailto:[EMAIL PROTECTED]
> MySQL really should throw an exception/error rather than just quietly > trim your data and accept it. When your data is critical, and your > business depends on it, you can't have bad data quietly going > into the database. The client software ought to be range-checking the data before sending it to the database. If the client isn't even doing that kind of minimal-effort check, how likely is it to be checking for exceptions? That's not to say that an error or exception is a bad idea, but MySQL may be constrained here by what the SQL standard says to do; I'm not sure. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
