Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: FW: Surrogate keys (Was: enums)
- From: Josh Berkus <josh(at)agliodbs(dot)com>
- To: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: FW: Surrogate keys (Was: enums)
- Date: Wed, 18 Jan 2006 19:13:10 -0800
- Message-id: <200601181913.11349.josh@agliodbs.com> <text/plain>
Dann, > The primary key should be immutable, meaning that its value should not be > changed during the course of normal operations of the database. Why? I don't find this statement to be self-evident. Why would we have ON UPDATE CASCADE if keys didn't change sometimes? > At any rate, the use of natural keys is a mistake made by people who have > never had to deal with very large database systems. Oh, I guess I'm dumb then. The biggest database system I ever had to deal with was merely 5 TB ... Anyway, my opinion on this, in detail, will be on the ITToolBox blog. You can argue with me there. -- Josh Berkus Aglio Database Solutions San Francisco
- References:
- Re: FW: Surrogate keys (Was: enums)
- From: Dann Corbit
- Re: FW: Surrogate keys (Was: enums)
- Prev by Date: Re: pgxs/windows
- Next by Date: suppress output for benchmarking
- Previous by thread: Re: Surrogate keys (Was: enums)
- Next by thread: Re: Surrogate keys (Was: enums)
- Indexes: