On Wednesday 31 August 2005 14:00, Joost Kraaijeveld wrote:
| So I cannot dump/restore/alter table. I was hoping that piping the text
| from stdout to psql that a valid conversion to unicode would take place
| but apparently that is not the case.
|
| Any other ideas?
maybe the recode utility can
On Wednesday 31 August 2005 14:09, Thomas Pundt wrote:
| maybe the recode utility can help then? Something like
|
| pg_dump -t artik munttest | recode latin1..utf | psql muntfinal
sorry to follow up on myself, but that command should read
pg_dump -t artik munttest | recode latin1..utf8 |
Joost Kraaijeveld [EMAIL PROTECTED] writes:
I am afraid that the problem is more complex. The original database
(which is created with SQL_ASCII) contains invalid byte sequences in
some columns (target database created with UNICODE):
There is no magic bullet to make bad data better. If the
On Wed, 2005-08-31 at 14:14 +0200, Thomas Pundt wrote:
pg_dump -t artik munttest | recode latin1..utf8 | psql muntfinal
Because the source encoding is unknown (the actual source database was
an ODBC source without known encoding that was copied with a C++ written
to a SQL_ASCII PostgreSQL
On Wed, 2005-08-31 at 10:29 -0400, Tom Lane wrote:
Joost Kraaijeveld [EMAIL PROTECTED] writes:
If, as seems more likely, there's a mishmash of different encodings then
you are in for some pain. At the minimum you'll have to separate out
Yep. The original database (which is copied to an
