Keith Gaughan wrote: > > As I said, I'm not defending MySQL. I'm saying that the behaviour of > NULLs in SQL is, well, buggered. Attacking a DBMS, any DBMS on the way > it handles them in various situations is a bit like shooting fish that > are fastened to the barrel of your gun. > > The thing is, the overloading of NULL in various DBMSs probably made > sense at the time. Just to taking the situation with MySQL, there are > times where you're inserting a new record and you may or may not want > the default value, but you'll only know at run time. > > A better solution would be to have a "USE_DEFAULT" keyword for that > particular kind of null value or something like that, but extending the > DML like that can be argued against easily too.
LOL Did you know that SQL has a DEFAULT keyword exactly for that purpose? The problem is MySQLs implementation of DEFAULT, not the standard. > I'm not saying that it's good. I'm just saying that its behaviour is no > worse than that of any other DBMS when it comes to NULLs. MySQLs behaviour is worse. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:208222 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
