On Fri, Jun 03, 2005 at 16:04:26 -0500,
Peter Fein <[EMAIL PROTECTED]> wrote:
>
> Ok, this makes a lot of sense & is just cleaner. Would you continue to
> do it this way if there were around a dozen derived tables (most with
> one or two columns)? I remember reading somewhere (perhaps the PG
>
Tom Lane wrote:
> Peter Fein <[EMAIL PROTECTED]> writes:
>
>>Let's say I have a base table B (with a PK id, say) and two derived
>>tables D1 & D2 (with different cols). For a given B.id, I'd like to
>>allow only a corresponding row in *either* D1 or D2, but not both. Any
>>suggestions on how to
On Fri, Jun 03, 2005 at 14:09:32 -0500,
Peter Fein <[EMAIL PROTECTED]> wrote:
> Hi-
>
> Let's say I have a base table B (with a PK id, say) and two derived
> tables D1 & D2 (with different cols). For a given B.id, I'd like to
> allow only a corresponding row in *either* D1 or D2, but not both.
Peter Fein <[EMAIL PROTECTED]> writes:
> Let's say I have a base table B (with a PK id, say) and two derived
> tables D1 & D2 (with different cols). For a given B.id, I'd like to
> allow only a corresponding row in *either* D1 or D2, but not both. Any
> suggestions on how to do this? Should I not
Hi-
Let's say I have a base table B (with a PK id, say) and two derived
tables D1 & D2 (with different cols). For a given B.id, I'd like to
allow only a corresponding row in *either* D1 or D2, but not both. Any
suggestions on how to do this? Should I not be using inheritance at all?
My thought
