From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Default encoding for new databases |
Date: | 2005-12-09 11:04:57 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7E824@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----Original Message-----
> From: pgadmin-hackers-owner(at)postgresql(dot)org
> [mailto:pgadmin-hackers-owner(at)postgresql(dot)org] On Behalf Of
> Peter Eisentraut
> Sent: 08 December 2005 23:04
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] Default encoding for new databases
>
> pgadmin3 proposes UTF8 as the default for new databases.
> While this is
> undoubtedly a contribution to world peace, it's also an invitation to
> create broken databases. The default encoding should be the encoding
> of template1 (or alternatively the template database chosen by the
> user) so that it matches the initialized locale. This is how the
> command line works. Other combinations will lead to databases with
> unusable sorting behavior. Please correct that.
Thanks, fixed (though I used template0 to get the default as it's less
likely to get dropped and possibly recreated in a different encoding).
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2005-12-09 11:18:56 | Re: SVN Commit by dpage: r4809 - branches/REL-1_4_0_PATCHES/pgadmin3/i18n/fr_FR |
Previous Message | svn | 2005-12-09 11:02:49 | SVN Commit by dpage: r4817 - in trunk/pgadmin3: . src/dlg |