Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: referential integrity and defaults, DB design or trick
- From: Richard Huxton <dev(at)archonet(dot)com>
- To: Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>
- Cc: pgsql-general(at)postgresql(dot)org
- Subject: Re: referential integrity and defaults, DB design or trick
- Date: Fri, 21 Dec 2007 08:19:08 +0000
Ivan Sergio Borgonovo wrote:
The default property (that is actually made by several fields) in my case is not completely homogeneous with the others, because it has a double meaning.It is cleaner to split the meanings and the data.
It usually is. A lot of the design decisions you can regret a year or two down the line are from trying to use one value for two purposes.
-- Richard Huxton Archonet Ltd
- Follow-Ups:
- Re: referential integrity and defaults, DB design or trick
- From: Ivan Sergio Borgonovo
- Re: referential integrity and defaults, DB design or trick
- References:
- referential integrity and defaults, DB design or trick
- From: Ivan Sergio Borgonovo
- Re: referential integrity and defaults, DB design or trick
- From: Ivan Sergio Borgonovo
- Re: referential integrity and defaults, DB design or trick
- From: Erik Jones
- Re: referential integrity and defaults, DB design or trick
- From: Ivan Sergio Borgonovo
- Re: referential integrity and defaults, DB design or trick
- From: Richard Huxton
- Re: referential integrity and defaults, DB design or trick
- From: Ivan Sergio Borgonovo
- referential integrity and defaults, DB design or trick
- Prev by Date: Re: settings for 8.2.5 on Mac OS X 10.4.11
- Next by Date: Machine spec 64-bit/32 GB RAM
- Previous by thread: Re: referential integrity and defaults, DB design or trick
- Next by thread: Re: referential integrity and defaults, DB design or trick
- Indexes: