From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ray O'Donnell <ray(at)rodonnell(dot)ie>, 'PostgreSQL' <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Overlapping timestamptz ranges with priority |
Date: | 2021-06-29 21:49:14 |
Message-ID: | 5e7b07f6-5bc7-a0e7-86af-04a63c117764@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6/29/21 2:30 PM, Ray O'Donnell wrote:
> On 29/06/2021 22:10, Adrian Klaver wrote:
>>
>> The queued bookings are for a particular aircraft or a particular time
>> slot?
>
> They're for an aircraft. On the old system, they could only be for a
> slot - so if someone had booked, say, a two-hour slot, then anyone
> queued behind them could only queue for the same two hours. I'd like to
> make the new system more flexible, hence the potentially overlapping
> ranges.
If I'm following correctly then:
1) Under old system there where preset two hour slots over a day period,
where the period was say 8:00 to 16:00
2) You now want to allow user defined two hour slots over the same
period, where a slot can't start before 8:00 or end after 16:00.
3) First to file gets the slot.
4) Because of turn around considerations a user can't pick up the
remaining hour of an overlap. As example in the case of time slots of
10:00 - 12:00 and 11:00 - 13:00 for a particular plane where the second
slot was the later one filed the user can't get 12:00 - 13:00.
>
> Ray.
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Yi Sun | 2021-06-30 06:33:10 | postgresql version 13 repo question |
Previous Message | Ray O'Donnell | 2021-06-29 21:30:30 | Re: Overlapping timestamptz ranges with priority |