Thanks Paul - I'll have to create a switch to identify...<br><br>Thanks for the prompt response...<br><br><br><br><div class="gmail_quote">2008/5/29 Paul Ramsey <<a href="mailto:pramsey@cleverelephant.ca">pramsey@cleverelephant.ca</a>>:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hilarity ensues, same issue being debated in another thread.<br>
<br>
In your case, no, there's probably no way around it. query is<br>
implemented as a FILTER, and filter gets passed directly to the<br>
underlying data store as SQL. The syntax for FILTER in shape files is<br>
mapserver specific, the syntax for PostGIS filter is PostgreSQL<br>
specific.<br>
<br>
Store all your data in postgis :)<br>
Or, more hackily, name your layers based on their storage type.<br>
pg_layer1, shp_layer2, etc.<br>
<br>
Sorry!<br>
<br>
P<br>
<div><div></div><div class="Wj3C7c"><br>
On Thu, May 29, 2008 at 9:24 AM, Mike Saunt <<a href="mailto:mikesaunt@gmail.com">mikesaunt@gmail.com</a>> wrote:<br>
> Hi All<br>
><br>
> We have an application that calls MapServer CGI from C# which creates<br>
> regular expressions for qitem (itemnquery etc) - basically when calling a<br>
> shape file all is good but not with PostGIS<br>
><br>
> uniqueid~'(a|A)(b|B)(c|C)123' = good for postgis<br>
><br>
> [uniqueid]=~/(a|A)(b|B)(c|C)123/ = bad for postgis (good for mapserver)<br>
><br>
> Does anyone know a way around - the calling app doesn't necessarily know<br>
> whether the base layer is PostGIS or OGR or Shape etc<br>
><br>
> Cheers<br>
> Mike<br>
><br>
><br>
</div></div>> _______________________________________________<br>
> mapserver-users mailing list<br>
> <a href="mailto:mapserver-users@lists.osgeo.org">mapserver-users@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
><br>
><br>
</blockquote></div><br>