This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] Proposal to allow UTF8
- Previous message (by thread): [db-wg] Proposal to allow UTF8
- Next message (by thread): [db-wg] Proposal to allow UTF8
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Fri Apr 17 14:54:19 CEST 2015
Hi all, On Fri, Apr 17, 2015 at 12:46:25PM +0000, Shane Kerr wrote: > On Fri, 17 Apr 2015 12:18:04 +0200 > Piotr Strzyzewski <Piotr.Strzyzewski at polsl.pl> wrote: > > > Proposal: > > I propose to allow UTF8 in all free text attributes of all DB objects > > except in primary keys. > > I think it makes sense. > <snip> > > Personally I think it could be used for primary keys too, but that can > always be added later. Allowing UTF8 in datafields helps with the issues that Piotr mentioned, there is a big benefit for all if you can accurately input your personal name or company address. On the other hand lots of primary keys are used by computer programs that don't care about such data. They just need to expand AS-Королевство into a set of prefixes. wait, maybe it is easier to just leave that as AS-KINGDOM. :-) I think it is best to leave primary keys untouched as they are today. The proposal as set forth by Pitor will benefit humans, and it is my assessment that it does not harm existing computer programs. Kind regards, Job
- Previous message (by thread): [db-wg] Proposal to allow UTF8
- Next message (by thread): [db-wg] Proposal to allow UTF8
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]