Opened 17 years ago
Closed 17 years ago
#2067 closed defect (fixed)
CLASSITEMs are no longer case insensitive
Reported by: | hobu | Owned by: | hobu |
---|---|---|---|
Priority: | high | Milestone: | 5.0 release |
Component: | Input - Native SDE Support | Version: | 5.0 |
Severity: | normal | Keywords: | |
Cc: | banders@…, sdlime |
Description (last modified by )
As a result of the reworking that combined msSDELayerGetItems, msSDELayerInitItemInfo, and msSDELayerCreateItems, CLASSITEMs that do not have the same case as the column names no longer work. This needs to be fixed before the release.
Change History (12)
comment:1 by , 17 years ago
Cc: | added |
---|---|
Status: | new → assigned |
comment:3 by , 17 years ago
Description: | modified (diff) |
---|
string2list in maplayer.c needs to be doing strcasecmp instead of strcmp, I think.
comment:4 by , 17 years ago
diff -r1.114 maplayer.c 329c329 < if(strcmp(list[i], string) == 0) { ---
if(strcasecmp(list[i], string) == 0) {
comment:5 by , 17 years ago
diff -r1.114 maplayer.c 329c329 < if(strcmp(list[i], string) == 0) { --- > if(strcasecmp(list[i], string) == 0) {
comment:6 by , 17 years ago
I also added a check in mapsde.c to see if msWhichItems tacks another item onto the later->items list because it couldn't find it. The way SDE works now, *all* of the items descriptions are gotten from the table(s) and put on the list. We should consider reworking or even removing msWhichItems if it existed only to server SDE's previous behavior.
comment:8 by , 17 years ago
I think the case insensitive match should be ok. Everything else is already that way. Can you apply and try?
steve
comment:10 by , 17 years ago
Milestone: | → 5.0 release |
---|
How can we test that this didn't have any bad effects?
comment:11 by , 17 years ago
Run a few mapfiles with postgis, shapefile and OGR sources and see if anything breaks... ;-)
comment:12 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Haven't found any problems. We can reopen if something shows up.