One or Both Foregin Keys - Mailing list pgsql-general

From Dennis Gearon
Subject One or Both Foregin Keys
Date
Msg-id 4092E26F.2070302@fireserve.net
Whole thread Raw
Responses Re: One or Both Foregin Keys
List pgsql-general
I am working on a design where a location for something can have:

    Fully qualified address with even building names, room numbers, and
booth numbers.
**-OR-**
    GPS location
**-OR-**
    Both

Other than triggers, is there a way to enforce this using tables and
primary keys?

I imagine an address table, and then

either a some sort of intermediate table,  in a one to many
relationship, GPS to Addresses,
or the correct columns in the address table.

Either way, I don't see a normal way to enforce EITHER or BOTH without a
trigger.

Thanks in Advance.

pgsql-general by date:

Previous
From: Rachel McConnell
Date:
Subject: "out of memory" error
Next
From: Sean Shanny
Date:
Subject: Re: "out of memory" error