No strong opinion/preference for me...
On 11-09-21 01:20 PM, Tamas Szekeres wrote:
Hi Devs,
We have some problems due to the recent changes in the SQL expression
parser which is related to the change in the implicit type conversion
behaviour.
Formerly we could safely use the following statement:
select * from mytable where ogr_fid in ('1100','1101','1102')
If the data type of ogr_fid is an integer or float then the expression
evaluator has converted the string constants to numeric values implicitly.
As of 1.8 the parser reports an error due to the incompatible types in
the expression.
I've added a ticket #4259 <http://trac.osgeo.org/gdal/ticket/4259>
related to this problem including a patch to handle these string to
numeric conversions.
However I'm a bit uncertain whether some other conversions should also
be supported or not. Having a larger number of conversion rules we might
probably think about rewriting the current approach by using a more
generic implementation.
Any ideas?
Best regards,
Tamas
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
--
Daniel Morissette
http://www.mapgears.com/
Provider of Professional MapServer Support since 2000
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
