Comments on: Chicago PHP User Group Report http://www.rubygeek.com/2006/05/18/chicago-php-user-group-report/ Ruby, PHP, Python and Perl Thu, 20 Nov 2008 17:45:37 +0000 http://wordpress.org/?v=2.5.1 By: Nola http://www.rubygeek.com/2006/05/18/chicago-php-user-group-report/#comment-22 Nola Fri, 19 May 2006 00:22:00 +0000 http://www.rubygeek.com/?p=52#comment-22 Peter says: ---------- I can't post a comment to your blog because I don't have a blogspot account, so: I've heard ChiPHPug pronounced "chif-pug" and "shy-pug", those are both pretty cuite. The standard way to deal with keying distributed databases is to divide up the keyspace with stepping. So servers A, B, and C will generate keys (1, 4, 7), (2, 5, 8), and (3, 6, 9). Alternately you could just add a column named 'server' and stick an id in there, though that forces your application code to know about the different servers. - -- Peter Harkins - http://push.cx Peter says:
———-

I can’t post a comment to your blog because I don’t have a blogspot
account, so:

I’ve heard ChiPHPug pronounced “chif-pug” and “shy-pug”, those are both
pretty cuite.

The standard way to deal with keying distributed databases is to divide
up the keyspace with stepping. So servers A, B, and C will generate keys
(1, 4, 7), (2, 5, 8), and (3, 6, 9). Alternately you could just add a
column named ’server’ and stick an id in there, though that forces your
application code to know about the different servers.

- –
Peter Harkins - http://push.cx

]]> By: Richard Lynch http://www.rubygeek.com/2006/05/18/chicago-php-user-group-report/#comment-21 Richard Lynch Thu, 18 May 2006 22:49:00 +0000 http://www.rubygeek.com/?p=52#comment-21 ChiPHPug is pronounced: CHIFF pug where CH is like chair ChiPHPug is pronounced:
CHIFF pug
where CH is like chair

]]> By: Martijn Gorree http://www.rubygeek.com/2006/05/18/chicago-php-user-group-report/#comment-20 Martijn Gorree Thu, 18 May 2006 21:26:00 +0000 http://www.rubygeek.com/?p=52#comment-20 In case of the: "But for database keys... I'd have to have one master way to make sure each record created some where has a unique key. I guess one way is to have a master sequence table on the master server, and to save .. " You might want to read http://www.onlamp.com/pub/a/onlamp/2006/04/20/advanced-mysql-replication.html MySQL 5.ish has a solution. In case of the:

“But for database keys… I’d have to have one master way to make sure each record created some where has a unique key. I guess one way is to have a master sequence table on the master server, and to save .. ”

You might want to read http://www.onlamp.com/pub/a/onlamp/2006/04/20/advanced-mysql-replication.html

MySQL 5.ish has a solution.

]]>