Justin Deoliveira wrote: > Hi all, > > I have run into a situation I am not sure how to solve. What happens > when a binary operator runs into a null value. Right now the null value > gets converted to the string "null" and the comparison proceeds, this > leads to strange results. > > So what is one to do. I can think of a couple of options: > > 1. throw an exception > Let's try not to - that often takes down everything. > 2. evaluate the filter to false > Much better - only return true for things that are "in" the set. If one of the things you are testing ends up null - it obviously cannot meet the condition and should not be selected (ie false).
Does the specification cover this one way or another? > 2 makes sense in some cases, like PropertyIsEqualTo, but not really in > others like PropertyIsLessThan. > Still makes sense in PropertyIsLessThan - you cannot verify that for the feature in question the property is less than - so you better return false. > Anyone else have any thoughts? > Cheers, Jody ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
