David Griffiths wrote:
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.
David.
Mike Johnson wrote:
A value is not valid just because it fits into the defined field type. All input values should be validated before inserting. If you are getting sql errors on inserts and updates, you may have a poorly designed user interface. Duplicate key errors on inserts are probably the exception. They can be valuable in eliminating lock-read-insert-unlock loops. An insert error indicates an existing record. A relative update can then be safely made without locking or insert race conditions.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
