| From: | Richard Jones <rich(at)annexia(dot)org> |
|---|---|
| To: | Harald Fuchs <hf0923x(at)protecting(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: SQL ASCII encoding |
| Date: | 2006-04-11 20:15:30 |
| Message-ID: | 20060411201530.GA29483@furbychan.cocan.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 05, 2006 at 10:15:18PM +0200, Harald Fuchs wrote:
> In article <20060405135419(dot)GD18401(at)svana(dot)org>,
> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>
> > As a british user, latin9 will cover most of your needs, unless
> > ofcourse someone wants to enter their name in chinese :)
>
> Since british users don't use French OE ligatures or Euro currency
> signs, even latin1 would do.
However as a British PostgreSQL user, I would really like to encourage
the O.P. to use UNICODE for _every_ database.
My question: Is it possible to upgrade a database from ASCII to
UNICODE without dumping and restoring?
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2006-04-11 20:34:16 | Re: how to prevent generating same clipids |
| Previous Message | Simon Riggs | 2006-04-11 19:36:40 | Re: execution plan : Oracle vs PostgreSQL |