 |
 |
Archives of the TeradataForum
Message Posted: Thu, 24 Jan 2008 @ 13:06:58 GMT
Subj: | | Re: Confusing of the 'NOT LIKE' logic |
|
From: | | Dieter N�th |
David Clough wrote:
| For what it's worth, whenever this type of confusing arises here at TNT I always recommend starting off with reversing the logic | |
Of course you're right, but "NOT(a OR b)" translates to "NOT a and NOT b" and that's exactly what Ray wrote :-)
The only reason for missing rows in that case is three way logic involving NULLs. Adding "OR url_txt IS NULL" should solve it.
Dieter
| |