RE: Why Null?

["Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Perhaps it's a typo but your last subselect projects 'lord' from HMI264254,
instead of 'ord' as you have in the join subselect.

As for EXISTS clause:

update gdidivf/ecl set 
lnet=(select pfct1 from kevinr/hmi264254 where 
  ecl.lord=hmi264254.ord and ecl.lline=hmi264254.line) 
where EXISTS
(select pfct1 from kevinr/hmi264254 where 
  ecl.lord=hmi264254.ord and ecl.lline=hmi264254.line)

It ought to perform much better than an IN clause anyway.

Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i5/OS and OS/400
www.centerfieldtechnology.com
 

-----Original Message-----
Subject: Why Null?

I know I should be using an EXISTS or something else on this, but I just 
wanted an apples-to-apples comparison.  On the following SQL statement I 
now run it on a different machine.  The main file was saved at a different 
point in time from the other system.  When I run it on this system I am 
getting null errors that I didn't get on the other system.

update gdidivf/ecl set 
lnet=(select pfct1 from kevinr/hmi264254 where 
  ecl.lord=hmi264254.ord and ecl.lline=hmi264254.line) 
where (lord,lline) in 
      (select lord,lline from kevinr/hmi264254) 

Wouldn't the where clause stop pfct1 from ever being null?

Rob Berendt