As near as I can tell, SQL implementations generally use one of two different approaches for dealing with NaN:
postgres and oracle apparently treat all NaN values as equal and greater than any other values. I do not know if they have any performance penalty for using this approach, but since SQL implementations tend to be io bound it probably is a fairly minor thing in that context. Mysql and microsoft's tsql apparenty do not support NaN. Mysql converts NaN values to 0 and issues a warning when this happens. -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
