>On Wed, Jan 26, 2005 at 01:06:38PM -0600, Michael Giagnocavo wrote: >> Oh no, it does lots. Data coercion (i.e., corruption) is it's specialty. >> Insert a string into a number... and you get 0! Isn't that great? No more >> errors. MySql is for people who like Visual Basic's "On Error Resume >Next" >> (aka 'ignore all errors and just produce screwed up results'). >> >> http://sql-info.de/mysql/gotchas.html >> >> I really like how Feb 31 works. > >If your code creates, or your data validation allows the above, then the >database you are using is the least of your worries. > >S
Sure, in an ideal world you'd never need any checking. Hell, typed languages are just stupid as well. Meanwhile, smaller things might go unnoticed. A change to the DB design that's thought to be OK? If you think that your DB should never ever have to kick back errors, then you've worked on amazing teams, or never on a team that did a lot of development against a DB. -Michael _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
