Re: Partial foreign keys, check constraints and inheritance - Mailing list pgsql-general

From Jim C. Nasby
Subject Re: Partial foreign keys, check constraints and inheritance
Date
Msg-id 20051122183825.GR19279@pervasive.com
Whole thread Raw
In response to Re: Partial foreign keys, check constraints and inheritance  (Eric E <whalesuit@gmail.com>)
List pgsql-general
On Thu, Nov 17, 2005 at 02:21:33PM -0500, Eric E wrote:
> >maybe you can solve it adding a new col and allow both to contain null
> >values.
> >
> >if these are not mutually exclusive you can avoid a check if they are
> >check that if one has a non-null value other has null...
>
>
> I did think about that, but I disliked the idea of two fields of nulls for
> every one full field.... maybe it's not as bad a way of doing it as I
> thought.

What's wrong with multiple NULL fields? It's probably the cleanest,
fastest way to do this...
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-general by date:

Previous
From: Bob Pawley
Date:
Subject: Re: Group By?
Next
From: Dennis Veatch
Date:
Subject: Re: Best way to represent values.