| From: | Adam Witney <awitney(at)sgul(dot)ac(dot)uk> |
|---|---|
| To: | "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: not valid character for Unicode |
| Date: | 2006-06-09 15:34:47 |
| Message-ID: | 44899517.4080406@sgul.ac.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> For migration, you should pg_dump- it's not clear from your email whether
> you are doing that. If you typed up some sql in Windows which you want to
> load into postgres, you might try:
> set client_encoding to 'LATIN1';
> at the top of your script.
yes this was how i spotted the problem. If i pg_dump from 7.4 and then
try to load into 8.1 these characters cause errors.
This data was generated on windows though as you say
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2006-06-09 15:40:52 | Re: Fabian Pascal and RDBMS deficiencies in fully implementing |
| Previous Message | Adam Witney | 2006-06-09 15:32:35 | Re: not valid character for Unicode |