Let's decide that a little bit later... Another anomaly that I notice everywhere; return module.newValueBuilder( TPoint.class ).prototype();
This is invalid (read unstable/unsupported) use of prototypes, since you don't instantiate them. Is it because you where unsure of the TransientComposites or how/when to make them into ValueComposites. I recommend that Values are used, due to the nature of the datatypes, but right now, they are broken... Any comments before I fix the rest (already sorted out the many Builders)? Cheers On Wed, Jun 3, 2015 at 10:45 PM, Jiri Jetmar <[email protected]> wrote: > Hi Niclas, > > this ST_XX follows the http://en.wikipedia.org/wiki/DE-9IM and > http://en.wikipedia.org/wiki/Simple_Features standards that are indeed > "SQL" related. I used this expression to be similar with e.g. PostGIS, > means when someone knows how to use spatial expressions on PostGIS, > he should be able to understand the Apache Zest approach. > > But clearly I can "lowercase" the ST_Xx expressions in the code. > > Cheers, > jj > > 2015-06-03 16:22 GMT+02:00 Niclas Hedhman <[email protected]>: > > > Jiri, > > There is one thing that bothers me; ST_Within and similar doesn't follow > > the Java convention at all. I have researched and seen that many DBs uses > > this, but don't you think we should lower case st_ instead for methods? > > > > > > Cheers > > -- > > Niclas Hedhman, Software Developer > > http://zest.apache.org - New Energy for Java > > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
