James Smith wrote: >>Why allow a INT(13)? So you can allow an INT(1). If you have > > Not true at all, if we are dealing with character length and the maximum > value for an INT is 4294967295 the INT(1) to INT(10) should work, but > INT(13) should throw an error.
The number behind the INT is a display mask. It is about formatting the data, it does not have any significance on accepted values for the field. And we all know that formatting should be handled in the frontend, so it is a useless feature. > No program should accept erroneous values > and then make up things to do with them because you then get dumb ass > results, if the value is invalid an error should be thrown. I agree, throwing errors is one of the most important features of any program: it tells you something is wrong. It is one of the most important reasons why I dislike MySQL. >> True/false, why not use just one bit for it? > > I don't know, why not? Because a bit does not accept the literals TRUE and FALSE. If you want to store a boolean value, use a boolean datatype. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Sams Teach Yourself Regular Expressions in 10 Minutes by Ben Forta http://www.houseoffusion.com/banners/view.cfm?bannerid=40 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:183344 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
