Re: Overlapping timestamptz ranges with priority - Mailing list pgsql-general

From Ray O'Donnell
Subject Re: Overlapping timestamptz ranges with priority
Date
Msg-id 8d6a1323-1214-1f54-4c5c-3dde6c346e54@rodonnell.ie
Whole thread Raw
In response to Re: Overlapping timestamptz ranges with priority  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: Overlapping timestamptz ranges with priority  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
On 28/06/2021 00:52, Adrian Klaver wrote:
> On 6/27/21 3:41 PM, Ray O'Donnell wrote:

>> Here's a slightly simplified example:
>>
>>
>> create table bookings (
>>      booking_id bigint not null,
>>      booking_time tstzrange not null,
>>
>>      constraint bookings_pk primary key (booking_id)
>> );
> 
> It seems to me this is missing some reference to what is being booked 
> e.g. room number.

Yes, indeed - I left out everything except what was immediately relevant 
to my problem. The real table is actually for booking aircraft - it's 
for the local flying club of which I'm a member - so there are columns 
for aircraft registration, member details, etc.

Ray.

-- 
Raymond O'Donnell // Galway // Ireland
ray@rodonnell.ie



pgsql-general by date:

Previous
From: Dolors Segura
Date:
Subject: pg_restore disable-triggers current session
Next
From: Marc Mamin
Date:
Subject: schema prefixes in default values (was RE: removing "serial" from table definitions).