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