Bug in OGR_L_SetAttributeFilter with long queries

[jsaiz]

This is code extracted from my web-application, from the server part.

Selection="ogc_fid IN (574,587,584)";

err=OGR_L_SetAttributeFilter(poLayer,Selection);

where ogc_fid is an unique identifier. This code is working perfectly until the list grows. When the list has more than ten elements, the program blocks. The number of elements change, so i think that it could be a problem with the length of the array.

note: I have done the services in php and libs in C, and test them in gdal version 1.4.3 over a fedora core 6 (64 bits)and in gdal version 1.3.1 over fedora core 4(32 bits)

[Even Rouault]

Which OGR driver is used by your poLayer object ? Is it specific to that driver or to all drivers ? Could you also test against a recently released GDAL version, for example 1.5.3 ? Any chance that you can reproduce this with a simple ogrinfo command on your dataset with the -where command line option and attach a simple dataset to reproduce it ?

I ask that because I can run successfully the following command on a PostGIS table:

apps/ogrinfo -ro -al PG: apt -where "ogc_fid in (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,32,33,34,35,36,37,38,39,40,41,42,43,44,45)"

[warmerdam]

We really need additional information to proceed on this ticket (as noted above).

[warmerdam]

Closing for lack of followup from the reporter.