[mapguide-users] QueryOptions.SetFilter Changed?

[Tom Fukushima]

This looks to be a side effect of a defect fix in the SDF provider:
There was a defect in the SDF provider where comparisons were case
insensitive, however providers are supposed to do case sensitive
compares. The SDF provider was fixed sometime around March to be case
sensitive.  This means that when doing compares with the SDF provider
the Upper, Lower functions will need to be used.  For example:
Lower(NAME) LIKE '%ab%'.

 

Tom

 

From: mapguide-users-bounces at lists.osgeo.org
[mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Rock Beans
Sent: Friday, July 13, 2007 7:50 AM
To: MapGuide Users Mail List
Subject: Re: [mapguide-users] QueryOptions.SetFilter Changed?

 

I have run into the same thing. Not sure why it changed but yes the
UCASE function should help most people. Anyone know why this
functionality changed?

The Rock

On 7/12/07, Chris Gountanis <cgountanis at rand.com> wrote:

Seems the same example code that utilized push pins is case sensitive
now. Is there some documentation on the changes. The new code examples
for 1.2 RC2 seemed to leave out the search data and place push pins on
map functions. And Why?

 

Chris


_______________________________________________
mapguide-users mailing list
mapguide-users at lists.osgeo.org 
http://lists.osgeo.org/mailman/listinfo/mapguide-users

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20070713/cec110ba/attachment.html