| From: | Joseph Shraibman <jks(at)selectacast(dot)net> |
|---|---|
| To: | Barry Lind <blind(at)xythos(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Character Encoding WAS: ArrayIndexOutOfBoundsException in Encoding.decodeUTF8() |
| Date: | 2003-01-08 23:31:07 |
| Message-ID: | 3E1CB4BB.4080406@selectacast.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-jdbc |
Barry Lind wrote:
>
>
> Joseph Shraibman wrote:
>> I notice there is no way to change a database's encoding. If I just
>> change the encoding type in the pg_database to latin1 will there be
>> data loss?
>
>
> The recommended way to do this would be to dump the contents of the
> database, create a new database with the desired character set and then
> import the data into that new database. I don't know if changing
> pg_database directly would work or not.
>
>
That didn't work. When I tried that Oné turned into Oné, which confuses me because I
thought my problem was that I was storing latin1 chars in a text field that was supposed
to only have the lower ascii bits. Oh well, I guess it is dump/reload time.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bjoern Metzdorf | 2003-01-08 23:57:08 | Re: too many Fatal Error 1: shutdown messages |
| Previous Message | Andreas Schlegel | 2003-01-08 22:56:17 | Re: Drop foreign keys |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joseph Shraibman | 2003-01-09 00:26:33 | Re: Character Encoding WAS: ArrayIndexOutOfBoundsException in Encoding.decodeUTF8() |
| Previous Message | Barry Lind | 2003-01-08 23:27:33 | Re: PreparedStatement.close() |