[OSM-dev] Restrict key names on order to retain reusability of OSM

Marcus Wolschon marcus at wolschon.biz
Wed Feb 13 09:06:38 GMT 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan Keller schrieb:
| as exotic street names as you wish. The consequences of this are
| problematic for all those more database schema oriented applications.
| It's about databases, XML and other formats outside the "OSM farm" you
| described which don't rely on this fancy general meta schema, and it
| goes like this:
|
| TABLE way_tags (
|   geometry ST_GEOMETRY,
|   id bigint(64) NOT NULL,
|   keyname varchar(255) NOT NULL,
|   value varchar(255) NOT NULL  // type
| )


You DO know that every decent database out there can store UTF8
and Unicode in varchars with no problem, do you?
varchar is allways used together with an encoding
that can be defined per field, table, database or
dbms and utf8 is a valid encoding in every database
I have ever worked with (quite a few).

You made a proposal, it was generally declined, now respect that.

Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHsrMef1hPnk3Z0cQRArhVAKCeaxFXl+oZZ853Pie/1hVe2iCKogCfSy32
LkrVXzDiIR3upOrj/9HbVgU=
=MHuk
-----END PGP SIGNATURE-----




More information about the dev mailing list