Hi Tatsuo,
Am Mittwoch, 20. Juli 2005 um 01:00 schrieben Sie:
TI> conversion tables. So if german umlauts are converted fine, there's no
TI> reason the conversion for german sharp s does not work.
TI> Marcus,
TI> Can you give me the exact error message from PostgreSQL when the
TI> conversio failed?
Well - actually, there IS no error message, convert() just returns an
empty sting. In detail, here's what I did:
-Set up PostgreSQL (Ascii)
-Imported the opengeodb
http://sourceforge.net/project/showfiles.php?group_id=132421
As they offer a PostgreSQL dump, I chose this one.
-Imported the dump using pgAdminIII
-Created a view that returns all german cities with ZIP and
opengeodb-locationID:
CREATE OR REPLACE VIEW orte_de AS
SELECT code.text_val AS plz, code.loc_id, town.text_val AS ort
FROM geodb_hierarchies hi, geodb_textdata state, geodb_textdata town, geodb_textdata code
WHERE hi.id_lvl2 = state.loc_id AND state.text_val = 'DE'::text
AND state.text_type = 500100001 AND town.loc_id = hi.loc_id
AND town.text_type = 500100000 AND code.loc_id = town.loc_id
AND code.text_type = 500300000;
So now I've got three columns: "plz" (zip), "ort" (city) and loc_id.
Assuming I want to retrieve cites in the Hamburg / Hannover area...
(perfect for this task, as they have pretty strange city names there
:)
SELECT plz, loc_id, ort, convert(ort using utf_8_to_iso_8859_1) as
ort_conv
from orte_de
where plz between 20000 and 30000
order by ort_conv
This query returns empty values for "ort_conv" if "ort" contains a
sharp s.
Btw, it seems like it is the same for "Ä" (Ä), have a look at
loc_id 25182.
--
Mit freundlichen Grüssen
Marcus Raphelt mailto:marcus@raphelt.de
