I wrote:
> You can run something like this over the plain text dump:
>
> sed -e 's/–/-/g' dump.sql >fixed.sql
Scrap that, it should of course be:
sed -e 's//-/g' dump.sql >fixed.sql
Yours,
Laurenz Albe
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to y
I realize I was too short, sorry.
NTPT wrote:
> but how to update affected columns ? error message does not provide single
> clue ( at least row name)
For every table and every column in the source database that might be
affected, try something like:
SELECT id, col FROM tab WHERE col LIKE E'%
but how to update affected columns ? error message does not provide single
clue ( at least row name)
And dump-restore ? It do not underestand how it could help.. dumped as
unicode restore as unicode = I am at the same point ... dumping as latin2
and restore to utf8 will end with the some e
NTPT wrote:
> but how to solve this in existing database ?
Either update all affected columns in the source database
or edit the database dump...
Yours,
Laurenz Albe
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgres
Hi,
Thanx for explanation.
but how to solve this in existing database ?
-- Původní zpráva --
Od: Albe Laurenz
Komu: 'NTPT *EXTERN*' , pgsql-general@postgresql.org
Datum: 25. 11. 2015 12:54:17
Předmět: Re: [GENERAL] Query failed: ERROR: character with byte sequence 0xc
NTPT wrote:
> I need help.
>
> pg_exec(): Query failed: ERROR: character with byte sequence 0xc2 0x96 in
> encoding "UTF8" has no
> equivalent in encoding "WIN1250"
>
> It is a strange. First there was a database with latin2 encoding.
>
> to this database connect an aplicaton with "set client e
Hi, all.
I need help.
pg_exec(): Query failed: ERROR: character with byte sequence 0xc2 0x96 in
encoding "UTF8" has no equivalent in encoding "WIN1250"
It is a strange. First there was a database with latin2 encoding.
to this database connect an aplicaton with "set client encoding to win1250"
