| From: | Bill Moran <wmoran(at)collaborativefusion(dot)com> |
|---|---|
| To: | Moritz Onken <onken(at)houseofdesign(dot)de> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Using PK value as a String |
| Date: | 2008-08-12 15:04:16 |
| Message-ID: | 20080812110416.8e0d6e1c.wmoran@collaborativefusion.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
In response to Moritz Onken <onken(at)houseofdesign(dot)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(at)collaborativefusion(dot)com
Phone: 412-422-3463x4023
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dforums | 2008-08-12 15:06:38 | Re: Distant mirroring |
| Previous Message | Merlin Moncure | 2008-08-12 14:29:17 | Re: Using PK value as a String |