On Mon, Jul 19, 2010 at 10:54 AM, Frank Warmerdam <[email protected]>wrote:
> Ragi Burhum wrote: > >> Would it make sense instead of implementing a SetDesiredFields(..) to >> implement a SetSubFields(string fieldnames) where the function >> takes a comma delimited list of subfields and then those are parsed by the >> shapefile driver to find out which field values to fetch? That way, for >> other drivers that have a SQL based underlying datastore, the way they would >> implement that fetching behavior would be by putting that content between >> the SELECT and the FROM portion. >> > > Ragi, > > I don't get the distinction here. Why can't the RDBMS based providers > just construct their SELECT clause based on the names of the fields > selected with SetDesiredFields()? They could. I just though just pushing the string directly would be easier from an API point of view and from an implementation perspective. Maybe it is just personal preference and I am mistaken. Thanks, - Ragi
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
