On Tue, Dec 1, 2009 at 5:32 PM, Simon Nuttall <[email protected]> wrote: > I have tracked down a duplicate entry problem to two tag keys that > have the different capitalisation: > > <node id="568478319" version="1" timestamp="2009-11-22T16:29:08Z" > uid="192124" user="Tony0" changeset="3187836" lat="50.6536544" > lon="-3.8970201"> > <tag k="historic" v="archaeological_site"/> > <tag k="Historic" v="Ruin"/> > <tag k="name" v="Three Boys"/> > <tag k="wpt_symbol" v="Dot"/> > </node> > > How should I fix up the table definition (I'm using MySQL) to skip over this? > Currently: > > CREATE TABLE `current_node_tags` ( > `id` bigint(64) NOT NULL, > `k` varchar(255) NOT NULL default '', > `v` varchar(255) NOT NULL default '', > PRIMARY KEY (`id`,`k`) > -- , > -- CONSTRAINT `current_node_tags_ibfk_1` FOREIGN KEY (`id`) > REFERENCES `current_nodes` (`id`) > ) > > Am I OK to change it from PRIMARY KEY to just KEY ?
How is that a problem for MySQL? "h" and "H" have different binary representations and are thus different keys, are they now? Marcus _______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
