NULL bites me worst when I do an OUTER JOIN between tables, then include a filter on a column in the table that's the OUTER (nullable) portion of the JOIN, effectively defeating the point of doing the OUTER in the first place.
On Wed, Sep 30, 2015 at 12:19 PM, AndyHC <[email protected]> wrote: > On 30/09/2015 16:30, Vince Teachout wrote: >> >> One of the biggest bite-my-butts I constantly deal with is coming up with >> a null value instead of a number, because somewhere in one of the records >> I'm adding, there is a null and I forgot to NVL() it... > > > +1 > > [excessive quoting removed by server] _______________________________________________ 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/CACW6n4up6YVvvg1LGwx7+SK0DB1s-XH+EocnyZ1ENnwvM=q...@mail.gmail.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.
