On 3 January 2012 13:07, Ari Jolma <[email protected]> wrote: > On 01/03/2012 02:45 PM, Mateusz Łoskot wrote: >> On 3 January 2012 11:07, Jukka Rahkonen<[email protected]> wrote: >>> >>> I took the successful query sent by Ari from the TinyOWS log and copied >>> it literally into Windows and this way it works: >>> >>> -where name='Hämeenkylä' >> >> Windows Command Prompt can work with UTF-8 characters if you change >> codepage to UTF-8: >> >> 0) Open new prompt (cmd.exe) >> 1) Change font to Lucida Concole >> 3) chcp 65001 >> >> And OGR can consume filter without problems: >> >> -where "name=\"Hämeenkylä\"" >> >> Note, the \"\" is needed to not to confuse OGR SQL compilers, >> otherwise value Hämeenkylä >> will be parsed as OGR SQL type SNT_COLUMN instead of SNT_CONSTANT for >> field value. > > > Is that really so?
I have checked the two variants under debugger and that's what I see, as far as I look at right place. > At least in PostgreSQL " and ' have different uses. " is > used for column names, which are not all lowercase and without special > characters and ' is used for string constants (as in this case). Perhaps parser gets confused by extended ASCII or non-ASCII characters, then the meaning of " and ' is affected. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
