| 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: | Re: Character Encoding WAS: ArrayIndexOutOfBoundsException in Encoding.decodeUTF8() |
| Date: | 2003-01-09 00:26:33 |
| Message-ID: | 3E1CC1B9.6060009@selectacast.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-jdbc |
Joseph Shraibman wrote:
> 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.
Acutally it did. My test data was flawed. What didn't work is editing the dump to change
the type to unicode.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Boget, Chris | 2003-01-09 00:37:13 | How can I do this? |
| Previous Message | Bjoern Metzdorf | 2003-01-08 23:57:08 | Re: too many Fatal Error 1: shutdown messages |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2003-01-09 03:02:15 | Re: 7.3 Prepared statements |
| Previous Message | Joseph Shraibman | 2003-01-08 23:31:07 | Character Encoding WAS: ArrayIndexOutOfBoundsException in Encoding.decodeUTF8() |