[OSM-dev] UTF8 problem with last night's daily .osc
Grant Slater
openstreetmap at firefishy.com
Sun Aug 31 01:08:11 BST 2008
Karl Newman wrote:
> If I recall correctly, the database column is not actually set for
> UTF-8 (but is double-encoded to return actual UTF-8 to the client...).
> Wouldn't it be a better long-term fix to change the database to UTF-8
> (or whatever), then presumably MySql wouldn't allow invalid sequences
> to be stored? Still would be a good idea to raise an error if the
> length was too long, though.
>
Yes, this is the case.
It's on the list of planned fixes for the 0.6 API. More on the wiki soon.
/ Grant
More information about the dev
mailing list