Re: Default encoding for new databases
От | Dave Page |
---|---|
Тема | Re: Default encoding for new databases |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7E824@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Default encoding for new databases (Peter Eisentraut <peter_e@gmx.net>) |
Список | pgadmin-hackers |
> -----Original Message----- > From: pgadmin-hackers-owner@postgresql.org > [mailto:pgadmin-hackers-owner@postgresql.org] On Behalf Of > Peter Eisentraut > Sent: 08 December 2005 23:04 > To: pgadmin-hackers@postgresql.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.
В списке pgadmin-hackers по дате отправления: