[fdo-internals] Request review of RFC28-AddStart/EndExpressionFunctions

[Dan Stoica]

This shortcut will make it difficult in the future to add more functions as agreed.
As opposed to having a PointN() implemented which makes easy to build on.

Dan.

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Robert Fortin
Sent: Wednesday, November 05, 2008 12:17 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request review of RFC28-AddStart/EndExpressionFunctions

Jason is correct.  The use case I'm concerned with is using single point geometry so I don't need the rest.
PointN(<single point geometry>, 1) is equal to the point geometry itself.

RF

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Wednesday, November 05, 2008 11:59 AM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request review of RFC28-AddStart/EndExpressionFunctions

You can have an X(geometry) that returns null for non-points.  Unless the EndPoint is important.

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Dan Stoica
Sent: Wednesday, November 05, 2008 08:53
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request review of RFC28-AddStart/EndExpressionFunctions

Then you cannot have only X(geometry). In addition a PointN() function is needed as well.

Dan.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20081105/5e4c35d9/attachment-0001.html