[fdo-internals] New RFC posted

[Thomas Knoell]

Hi Jason,

The proposed solution is close to the signature we currently support for the expression function Extract. It also is in-line with other functions where we accept an identifier from an enumeration to avoid having multiple functions that just differ in the kind of information it returns. But if the consensus in this discussion is to have functions for each of the date/time properties, then the RFC could be adopted.

Thanks

  Thomas

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Wednesday, November 12, 2008 1:52 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] New RFC posted

Interesting...

Would there be any interest in superseding this function with individual YEAR(), MONTH(), DAY(), etc functions?  This would be easier to parse in the expression definition, and the user wouldn't have to think about the return type (YEAR() always returns int, SECONDS() always returns double, etc.)

Jason

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Thomas Knoell
Sent: Tuesday, November 11, 2008 15:23
To: FDO Internals Mail List
Subject: [fdo-internals] New RFC posted

Hi,

I posted a new RFC (http://trac.osgeo.org/fdo/wiki/FDORfc29) related to a usability issue of the expression function EXTRACT. The proposed solution will redefine this expression function for easier use. Please review the RFC and let me know of any questions/issues/suggestions you may have.

Thanks

  Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20081112/d3c896c4/attachment.html