I guess you can not alter database encodng, so the way to change database
encoding can be following these steps:
1. Take the database dump for which you wish to change encodig using
2. Now drop the database
3. Recreate the database with the encoding you wish to
For exampe --> createdb testdb -e unicode
4. Check if the dump file created in the first step has any special
characters and do the required changes.
5. Now you can restore the dump file into the newly created database.
The advantage of using a Unicode database is that UTF-8 supports/includes
all known encodings at once. Therefore, in the process of development, it
can help you save time.
On 3/28/06, Keith Worthington <keithw(at)narrowpathinc(dot)com> wrote:
> Hi All,
> When I originally built a database I did not understand the ramifications
> choosing the encoding. Not knowing any better I chose SQL-ASCII. Since
> upgrading pgadmin3 to the latest release I am cautioned that I should
> switch to
> How do I go about changing the database encoding?
> Is UNICODE the 'best' choice for a general purpose database?
> Kind Regards,
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
In response to
pgsql-novice by date
|Next:||From: A. Kretschmer||Date: 2006-03-28 16:38:35|
|Subject: Re: plpgsql questions|
|Previous:||From: Michael Swierczek||Date: 2006-03-28 16:02:28|
|Subject: plpgsql questions|