In what situation would it be necessary use duplicate keys? If there's a need, can we reach the same goal without using it? I think duplicated keys can lead to database problems (e.g. performance) that can be avoid.
Julison. 2008/10/10 Matthias Julius <[EMAIL PROTECTED]> > Stefan de Konink <[EMAIL PROTECTED]> writes: > > > - I assumed that editors like JOSM, and their behavior was consistent > > and there is absolutely no useful use of duplicate keys. > > Actually, the editors are pretty consistent in not supporting > duplicate keys, but that doesn't mean that this wouldn't be useful. > > I hope nobody disputes that multiple values for one key can be very > useful. The question is how this should be implemented. > > IMHO, the most naturally implementation is to allow duplicate keys. I > consider delimited strings an acceptable workaround. Especially when > it is relied upon the user to do the delimiting. > > On a second thought, most duplicate values could be avoided by using > relations. > > Matthias > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/dev > -- Julison Mendonça.
_______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
