On 04/25/11 11:14 AM, SUBHAM ROY wrote:
While loading data from shape files, the default encoding type is
UTF8. It reports an error "couldn't convert to UTF8 ... change the
encoding to latin1 ... etc."
what reported this?
So my question is, if one table say T1 is loaded using UTF8 and the
While loading data from shape files, the default encoding type is UTF8. It
reports an error "couldn't convert to UTF8 ... change the encoding to latin1
... etc."
So my question is, if one table say T1 is loaded using UTF8 and the other
say T2 is loaded using say LATIN1, then does it impose any pro
Is there any chance of this being considered for 8.4 ?
Unfortunately I cannot provide patches myself as my
knowledge of C is next to nothing.
Thanks,
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
--
Sent via pgsql-general mailing list (pgsql
Sorry for the noise.
The problem is solved with the restart of the postgresql server.
Have a nice day.
Kaloyan Iliev
Kaloyan Iliev wrote:
Hi All,
I try to migrate a database from WIN1251 to UTF8 but
I have a problem dumping from WIN1251 to UTF8.
pg_dump -C -E 'UTF8' a > a_utf8.sql
pg_dump: S
Hi All,
I try to migrate a database from WIN1251 to UTF8 but
I have a problem dumping from WIN1251 to UTF8.
pg_dump -C -E 'UTF8' a > a_utf8.sql
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: could not load library
"/usr/local/lib/postgresql/utf8_and_cyrillic.so": dlopen
Steps :
export LANG=ru_RU.KOI8-r (locale was set properly)
initdb
createdb -E WIN tst
psql tst < tsearch2.sql
psql tst :
SET client_encoding to KOI8;
create table tst (name text, v tsvector);
insert ..
update tst set v = to_tsvector(lower(nm));
and i've got capitalized russian text in v (vec
