On Mon, Jan 12, 2015 at 06:29:32PM -0500, BladeOfLight16 wrote: > On Fri, Jan 9, 2015 at 6:16 PM, Paul Ramsey <pram...@cleverelephant.ca> > wrote: > > > Yes, I could see that as a reasonable interpretation. Just another in > > the large collection of corner cases opened up by allowing typed empty > > (my fault). The code probably just tests for empty and reflects the > > input back in that case. > > > > Just for the record, I don't see a problem with EMPTY. It's a legal > geometry definition (including by WKT). It makes just as much sense as > empty string, imo. (The fact Oracle treats empty string as NULL has driven > me a little batty on occasion.) I'm glad for the distinction. > > Do I need to file a bug report somewhere, or is this enough?
A ticket on trac would ensure it gets fixed (I think it's worth it). If you attach a patch that'd even happen fast! :) Thank you. http://trac.osgeo.org/postgis/ --strk; _______________________________________________ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
