[mapserver-dev] 6.0 release plan

[Lime, Steve D (DNR)]

Let me think on that. Actually I'd like to remove whichShapes() from mapscript and force users through a query method. I don't think
it's worth the headache to support that method. I should have never added it...

Steve

From: Tamas Szekeres [mailto:szekerest at gmail.com]
Sent: Tuesday, November 09, 2010 8:47 AM
To: Lime, Steve D (DNR)
Cc: mapserver-dev at lists.osgeo.org
Subject: Re: [mapserver-dev] 6.0 release plan


2010/11/9 Lime, Steve D (DNR) <Steve.Lime at state.mn.us<mailto:Steve.Lime at state.mn.us>>
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.



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?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20101109/0ea49c50/attachment.html