I downloaded today the full geoname files and I got an error on importing geoname n° 290557 (United Arab Emirates) as the data provided for column alternatenames does not fit in a varchar(4000) as specified in the spec.
By the way I did download the full file a few days ago and it was not too long at that time : this means the update is recent.
But the modification date for the geoname is still 2009-09-17 => question : does an update only on an alternate name of a geoname NOT change the modification date ?
Thanks for pointing this out. We have improved the automatic transliteration from foreign languages to ascii. The result of this transliteration is also included in the alteratenames list. This is the reason it was possible that the string was longer even though the toponym itself was not modified.
I have increased the size of the field in the doc to varchar(5000)