Opened 14 years ago
Closed 14 years ago
#3557 closed defect (fixed)
wfs filter and propertly islike on oracle layers
Reported by: | assefa | Owned by: | assefa |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | WFS Server | Version: | 5.6 |
Severity: | normal | Keywords: | |
Cc: | porath@… |
Description
From the mailing list (Holger Porath <porath@…>)
We are still having issues with using mapserver 5.6.5 as a wfs server together. When we submit a wfs getfeature filter request mapserver doesn't use the filter in the sql statement. It just searches all the objects in the database and applies the filter on the result. Thus, we are getting a timeout.
Here is our filter request:
Filter=<Filter><PropertyIsLike wildCard="%" singleChar="?" escape="ESC"><PropertyName>FS_FSZ</PropertyName><Literal>111</Literal></PropertyIsLike></Filter>
As you can see the filter for the attribute "FS_FSZ" is set to "111".
The debug log shows that this isn't used in the sql at all: Using this Sql to retrieve the data : SELECT fs_id, FS_GKNR, FS_FLNR, FS_FSZ, FS_FSN, FS_FSSTATUS, FS_ID, FS_FSRWERT_ABS, FS_FSHWERT_ABS, fs_koordinate FROM os_flst I expected to see a where clause like the following: where fs_fsz like "111" When we switch back to mapserver 5.0.0 we see the correct where clause in the debug log. So what are we doing wrong or is this a bug?
Attachments (1)
Change History (6)
comment:1 by , 14 years ago
comment:3 by , 14 years ago
latest pathc should fix 2 or more propertyislike on db type layers.
Peter please confirm after your tests. Thanks
comment:5 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Tested the patch and it is working now. Many Thanks.
I was able to reproduce the reproduce this. Fix should be in r10549. Please give it a try.