<div>Hi Devs,</div><div><br></div><div>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. </div><div><br></div><div>Formerly we could safely use the following statement:</div>
<div><br></div><div>select * from mytable where ogr_fid in ('1100','1101','1102')</div><div><br></div><div>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.</div>
<div><br></div><div>As of 1.8 the parser reports an error due to the incompatible types in the expression.</div><div><br></div><div>I've added a ticket <a href="http://trac.osgeo.org/gdal/ticket/4259">#4259</a> related to this problem including a patch to handle these string to numeric conversions.</div>
<div><br></div><div>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.</div>
<div><br></div><div>Any ideas?</div><div><br></div><div><br></div><div>Best regards,</div><div><br></div><div>Tamas</div>