It's actually something quite old, one of the first issues I encountered
with the project was the inconsistency between shapefile and postgres
backends.  I forgot that I haven't added this behavior back to the
converter since I rewrote the simplifier a while back.


On Mon, Feb 3, 2014 at 4:51 PM, Andrea Aime <andrea.a...@geo-solutions.it>wrote:

> Hi David,
> Is this something new? I'm asking bacause I got into this exactly out of
> CSS style filters, that do contain negations, without any null handling,
> and as a result upend up not painting the features with null values.
>
> I dont have the style handy now, but I can share it tomorrow if you want
> to have a look
>
> Cheers
> Andrea
> Il 03/feb/2014 21:49 "David Winslow" <dwins...@boundlessgeo.com> ha
> scritto:
>
> FWIW the simplifier in my CSS converter just adds (or removes) the IS NOT
>> NULL logic.  I've tried it a few ways and this seems the only way to be
>> consistent across two-state and three-state logic systems.
>>
>> Might be nice if GeoTools were to emulate three-state logic for in-memory
>> systems, but I'm not sure it's feasible to have three-state for all
>> backends.
>>
>>
>> On Mon, Feb 3, 2014 at 3:45 PM, Andrea Aime <andrea.a...@geo-solutions.it
>> > wrote:
>>
>>> On Mon, Feb 3, 2014 at 9:41 PM, Jody Garnett <jody.garn...@gmail.com>wrote:
>>>
>>>> I admit de morgan is a pain to implement, but I would find the result
>>>> more intuitive then null checks suddenly appearing.
>>>>
>>>
>>> Easier to read, yes, easier to index, maybe, but ... more intuitive?
>>> How do you explain a end user that he wrote "not(a > 3 and b = 5 and c
>>> <= 10)"
>>> and the code is running "a <=3 or b < 5 or b > 5 or c > 10" and that is
>>> fully equivalent,
>>> actually, it is better?
>>>
>>> Also, I still have to verify that what we discussed so far actually
>>> brings the database
>>> 3 state logic back to our 2 state one in a fully equivalent manner:
>>> think nested filters
>>> or combinations, I believe that once even one bit is unknown,
>>> everything just flips
>>> into that state, and that the only way to get out of it is to have
>>> explicit "is null", "is not null"
>>> statements...
>>> Have to check.
>>>
>>> Cheers
>>>  Andrea
>>>
>>>
>>> --
>>> == Our support, Your Success! Visit http://opensdi.geo-solutions.it for
>>> more information ==
>>>
>>> Ing. Andrea Aime
>>> @geowolf
>>> Technical Lead
>>>
>>> GeoSolutions S.A.S.
>>> Via Poggio alle Viti 1187
>>> 55054  Massarosa (LU)
>>> Italy
>>> phone: +39 0584 962313
>>> fax: +39 0584 1660272
>>> mob: +39  339 8844549
>>>
>>> http://www.geo-solutions.it
>>>  http://twitter.com/geosolutions_it
>>>
>>> -------------------------------------------------------
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Managing the Performance of Cloud-Based Applications
>>> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
>>> Read the Whitepaper.
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> GeoTools-Devel mailing list
>>> GeoTools-Devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>
>>>
>>
>>
>> --
>> David Winslow
>> Boundless - http://boundlessgeo.com/
>>
>


-- 
David Winslow
Boundless - http://boundlessgeo.com/
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to