[fdo-internals] RE: [fdo-trac] #516: FDO Core enhancement: support standard ORDER BY expressions

[Greg Boone]

That is somewhat true, RFC's are typically written by those who want to implement the change. However, asking for an enhancement request through a Trac item usually goes nowhere and lost in the great bin of unresolved Trac issues that keep getting pushed forward from release to release. If this change is really required, an RFC should be written and someone sign up to make the changes.

Greg

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer
Sent: Wednesday, April 29, 2009 11:52 AM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] RE: [fdo-trac] #516: FDO Core enhancment: support standard ORDER BY expressions

so with regards to the RFC process, is that how it really works?

to date is seems RFC's get written by the person who is going to
implement the changes

z

On Thu, Apr 30, 2009 at 1:41 AM, Greg Boone <greg.boone at autodesk.com> wrote:
> Correction...
>
> "If these is an enhancement request, you should write up an RFC."
>
> -----Original Message-----
> From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
> Sent: Wednesday, April 29, 2009 11:40 AM
> To: FDO Internals Mail List
> Subject: [fdo-internals] RE: [fdo-trac] #516: FDO Core enhancment: support standard ORDER BY expressions
>
> If these is an cement request, you should write up an RFC.
>
> Greg
>
> -----Original Message-----
> From: trac_fdo at osgeo.org [mailto:trac_fdo at osgeo.org]
> Sent: Wednesday, April 29, 2009 4:29 AM
> Cc: fdo-trac at lists.osgeo.org
> Subject: [fdo-trac] #516: FDO Core enhancment: support standard ORDER BY expressions
>
> #516: FDO Core enhancment: support standard ORDER BY expressions
> ---------------------------+------------------------------------------------
>   Reporter:  mwtoews      |       Owner:  gregboone
>       Type:  enhancement  |      Status:  new
>   Priority:  minor        |   Milestone:  3.5.0
>  Component:  FDO API      |     Version:  3.4.0
>   Severity:  3            |    Keywords:
> External_id:               |
> ---------------------------+------------------------------------------------
>  Searching through the fdo-user's list, I found some discussion and ticket-
>  worthy material on the topic of ordering data from the core API:
>  http://lists.osgeo.org/pipermail/fdo-users/2008-May/000943.html
>
>  The primary importance for me is the drawing order of stacked features. At
>  present, in AutoCAD Map3D we have no control how overlapping polygons are
>  drawn. One workaround is to create a database view on the server-side that
>  is linked to FDO/CAD, and the other is to break a single feature layer
>  into several layers to get the stacking correct. The preferred method
>  would be to use a single ordered feature class that is sored by (e.g.)
>  date, status, area, or some other feature attribute.
>
>  From a low-level perspective, it appears this is supported by some
>  providers using customized commands. This enhancement is aimed to bring
>  soring of data on 1 or more attribute columns to FDO Core, so it can be
>  supported by data providers.
>
>  See also, a similar "ORDER BY" enhancement request for QGIS:
>  https://trac.osgeo.org/qgis/ticket/1597
>
> --
> Ticket URL: <https://trac.osgeo.org/fdo/ticket/516>
> FDO <http://fdo.osgeo.org/>
> Feature Data Objects
>
> _______________________________________________
> fdo-internals mailing list
> fdo-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-internals
>
>



-- 
Zac Spitzer -
http://zacster.blogspot.com
+61 405 847 168
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals