From: | Ray O'Donnell <ray(at)rodonnell(dot)ie> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, 'PostgreSQL' <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Overlapping timestamptz ranges with priority |
Date: | 2021-06-28 10:05:32 |
Message-ID: | 8d6a1323-1214-1f54-4c5c-3dde6c346e54@rodonnell.ie |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)rodonnell(dot)ie
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Mamin | 2021-06-28 10:50:23 | schema prefixes in default values (was RE: removing "serial" from table definitions). |
Previous Message | Dolors Segura | 2021-06-28 09:57:51 | pg_restore disable-triggers current session |