From: Bill Moran <wmoran@collaborativefusion.com>
To: Moritz Onken <onken@houseofdesign.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: Using PK value as a String
Date: Tue, 12 Aug 2008 11:04:16 -0400
Message-ID: <20080812110416.8e0d6e1c.wmoran@collaborativefusion.com> (raw)
In-Reply-To: <1343069D-263F-4D99-BF7E-269C8F0E7F1F@houseofdesign.de>
References: <18986.60888.qm@web25807.mail.ukl.yahoo.com>
<48A15ECF.5030203@sime.com>
<87od3ywg4n.fsf@oxford.xeocode.com>
<0673579A-B049-4619-B6E4-EE427FB0DDBA@globalinn.com>
<1343069D-263F-4D99-BF7E-269C8F0E7F1F@houseofdesign.de>
In response to Moritz Onken <onken@houseofdesign.de>:
> We chose UUID as PK because there is still some information in an
> integer key.
> You can see if a user has registered before someone else (user1.id <
> user2.id)
> or you can see how many new users registered in a specific period of
> time
> (compare the id of the newest user to the id a week ago). This is
> information
> which is in some cases critical.
So you're accidentally storing critical information in magic values
instead of storing it explicitly?
Good luck with that.
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
wmoran@collaborativefusion.com
Phone: 412-422-3463x4023
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: wmoran@collaborativefusion.com, onken@houseofdesign.de
Subject: Re: Using PK value as a String
In-Reply-To: <20080812110416.8e0d6e1c.wmoran@collaborativefusion.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox