15 messages in com.mysql.lists.clusterRe: Will I have a runaway primary key...
FromSent OnAttachments
Jayson Larose04 Dec 2006 08:41 
mizi...@aim.com04 Dec 2006 09:20 
Jayson Larose04 Dec 2006 11:03 
Kevin Burton04 Dec 2006 13:28 
Adam Dixon04 Dec 2006 14:55 
Kevin Burton04 Dec 2006 15:23 
Jayson Larose04 Dec 2006 16:21 
Anatoly Pidruchny04 Dec 2006 17:23 
Kevin Burton04 Dec 2006 19:04 
Jayson Larose04 Dec 2006 20:51 
Anatoly Pidruchny04 Dec 2006 21:09 
mizi...@aim.com05 Dec 2006 08:56 
mizi...@netscape.net05 Dec 2006 09:10 
Stewart Smith12 Dec 2006 19:44 
Stewart Smith12 Dec 2006 19:46 
Subject:Re: Will I have a runaway primary key problem in the future if I do this?
From:Anatoly Pidruchny (apid@newxt.com)
Date:12/04/2006 05:23:18 PM
List:com.mysql.lists.cluster

Hello,

The data being returned from the SNMP servers are key->value pairs, but each individual server that is polled will be giving back the same keys, so you run into the same duplicate primary key issue if you try to base your primary key off 'description' as in my sample database spec.

Why not define a primary key consisting of the three columns: colo, server and description? Then there will be no duplicate primary key issue and no hidden BIGINT primary key.

Does this mean that as old, lower-ordered keys are deleted and new, higher-ordered keys are added to the database, the fields are actively being shifted amongst the various NDB nodes?

Yes, it does, and yes, they are.

Anatoly Pidruchny.