Re: [Gnumed-devel] loinc import

[Karsten Hilbert]

> >>>couldn't find a import of loinc to sql, so there's one in 
> >>>test-area/loinc directory for postgres. Some of the foreign language 
> >>>field values
> >>>will look funny, because incompatible unicode characters (for postgres) 
> >>>were excluded using the postgres string.printable list.
> I could change the locale of the operating system, but I've never done 
> it before, and I still don't know
> if that would make it work, so I just screened out the characters that 
> didn't fit my python installations
> locale , and that seemed to work. I just wanted to get the loinc 
> workable in my postgres installation as
> quick as possible.

What encoding/charset is that data in ? It should work IMO to
just treat the data as binary without operating on it and set
the client_encoding to whatever the encoding of the data is
(unicode/utf16 ?) As our database is set to be unicode this
*should* work - and I certainly have no trouble mixing
latin1/us-ascii in our unicode database.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346