On 5/31/05, Matt Robertson <[EMAIL PROTECTED]> wrote: > On 5/31/05, Bryan Stevenson <[EMAIL PROTECTED]> wrote: > > Of course MySQL allows NULLs in NOT NULL fields among other "features" ;-) > > Not that I want to work too hard to paw fresh kitty litter over this > lump of poop (i.e. I agree its a flaw), but all this really does is > allow some jackass to screw up prior to initial testing. Personally I > may put a null or a not null value into a field but I always make sure > I put in something that belongs there via a variety of tools at hand; > and never let the db decide -- on purpose, anyway -- whether I screwed > up or not.
What's the example of the situation you NULL issue -- a simple SQL example would help me figure out exactly what situation you're talking about. -- John Paul Ashenfelter CTO/Transitionpoint (blog) http://www.ashenfelter.com (email) [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:208133 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
