Re: Overlapping timestamptz ranges with priority
От | Ray O'Donnell |
---|---|
Тема | Re: Overlapping timestamptz ranges with priority |
Дата | |
Msg-id | 8d6a1323-1214-1f54-4c5c-3dde6c346e54@rodonnell.ie обсуждение исходный текст |
Ответ на | Re: Overlapping timestamptz ranges with priority (Adrian Klaver <adrian.klaver@aklaver.com>) |
Ответы |
Re: Overlapping timestamptz ranges with priority
|
Список | 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 по дате отправления: