[Mapserver-users] qstring - multiple values

[Jan Hartmann]

I would certainly like that as a feature request. Lots of maps out there 
with discrete or enumerative map items. I guess it could also be 
implemented faster than the equivalent logical expression.

Jan

Steve Lime wrote:
> Remember that qstring is a valid MapServer expression so it's more
> powerful than before, although with that power comes a bit of complexity
> and even cumbersomeness. You're not just limited to string matches. So,
> to do multiple matches you would craft a logical expression like ([item]
> in ('27001','27003',...)). I'm not sure if the in syntax is correct but
> you get the idea. If there is enough interest we could look into
> supporting expressions like:
> 
>   EXPRESSION [27001,27003,...]
> 
> and having MapServer recognize that as a list to be matched against a
> single ITEM. Sort of a shortcut logical expression. It would be
> implemented as a new expression type within the software. Thoughts?
> 
> Steve
> 
> 
>>>>Matthew Smith <matt at kbc.net.au> 08/06/03 09:03AM >>>
> 
> Fawcett, David wrote:
> 
>>When I had tried something like
> 
> '...mycgi?qstring=27001&qstring=27003&qstring=...'
> 
>>qstring appears to be set to only one value, the last value set in
> 
> the URL.
> 
>>David.
> 
> 
> Hmm  - looks like Mapserver doesn't handle multiples - you may need to
> 
> do something with Mapscript unless someone else can advise another way
> 
> of doing this (I'm familiar with query strings, not so much with 
> Mapserver ;-)
> 
> On the subject of query strings - can anyone tell me when Mapserver
> will 
> use/accept the semicolon separator rather than the deprecated
> ampersand? 
>   It took me AGES to work out why my query strings weren't working
> until 
> I followed an example to the letter and di it the old way.
> 
> Cheers
> 
> M
>