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?
Not sure what you code in, but in Java, you *HAVE* to catch SQLExceptions (or throw them up). Isn't it better to give the developer the option?
Also, most people who have replied seem to think that I/you are the author of the code.
If you use the MySQL client to do an IMPORT DATA (say as an export from another database), and you made a mistake in the DDL (data-definition-language) and used an INT when you should have used a BIGINT, you won't know.
David
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
