Archives of the TeradataForum

Message Posted: Thu, 26 Mar 2009 @ 16:14:36 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

I did some more checking and I have other queries that successfully compare null dates with the simple "<>" condition statement. For example, the query:

     SELECT
       O.close_date,
       I.close_date
     FROM
       F_LOAN O

       FULL OUTER JOIN V1_F_LOAN I
           ON O.ID_SRC = I.ID_SRC AND O.PARENTACCOUNT_SRC = I.PARENTACCOUNT_SRC

       WHERE
           o.close_date <> i.close_date

This query works perfectly and finds the close_date columns that differ. Again, I wonder why this one table is requiring the "NULL" tests when the other tables do not. The only difference that I know is how I created the table which was by using the "CREATE TABLE ... AS ... WITH DATA" statement. Is it possible by using that type of statement, the data was somehow stored differently than other tables where the data is imported into the tables? Copying data inside Teradata vs. Data being imported from the outside?

Again, the null comparisons fix the issue, but curious why it is needed for just this table when the other tables work correctly. Weird...

Shaun

	<Prev	Next>		<<First	<Prev	Next>	Last>>