Sure you're smart enough, Jeff . You're on the Profox list... ;-) NVL() is your friend and can make null checking/handling fairly trivial. And you need to handle nulls when you run queries using left or right joins; not just table structures.
-- rk -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Jeff Johnson Sent: Thursday, April 16, 2015 8:16 AM To: [email protected] Subject: Re: Nulls When importing data I need to test for an empty value and then replace it with something meaningful. I'm not smart enough to test for nulls and it also makes for too much code. Also, if I don't convert a null to something other than a null I can't insert a record into a table that doesn't accept nulls (which all of mine are). It is way easier for me to to change the tables to not accept nulls. YMMV On 4/16/2015 3:23 AM, Laurie Alvey wrote: > In my innocence, I wonder why you want to disallow NULLs? They are, IMHO, > the best way to hold unknown or irrelevant column values. > > Laurie > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/blupr10mb0451552b0a98258c6ee35214d2...@blupr10mb0451.namprd10.prod.outlook.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
