<br><br><div class="gmail_quote">2010/11/9 Lime, Steve D (DNR) <span dir="ltr"><<a href="mailto:Steve.Lime@state.mn.us">Steve.Lime@state.mn.us</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">When queryObj’s were introduced in 5.6 the mapscript interfaces
to the various query methods were unchanged. Users still passed the same
arguments and do not access a queryObj directly. Instead, a queryObj is
populated within the wrapper code based on the user arguments and the queryObj
is passed on to the underlying query function. I don’t see that changing.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><br></div></div></blockquote></div><br>I mean if I call whichShapes from mapscript how would I set queryObj to denote the purpose of the query? Or we would add some extra initialization for this in layer.i assuming a single row forward only access is taking place?<br>
<br><br>