<br><br><div class="gmail_quote">On Mon, Jul 19, 2010 at 10:54 AM, Frank Warmerdam <span dir="ltr"><<a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Ragi Burhum wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Would it make sense instead of implementing a SetDesiredFields(..) to implement a SetSubFields(string fieldnames) where the function<br>
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.<br>
</blockquote>
<br></div>
Ragi,<br>
<br>
I don't get the distinction here. Why can't the RDBMS based providers<br>
just construct their SELECT clause based on the names of the fields<br>
selected with SetDesiredFields()? </blockquote><div><br></div><div>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.</div>
<div> </div><div>Thanks,</div><div><br></div><div>- Ragi</div></div>