Re: SQL:2011 PERIODS vs Postgres Ranges?
От | Paul A Jungwirth |
---|---|
Тема | Re: SQL:2011 PERIODS vs Postgres Ranges? |
Дата | |
Msg-id | CA+renyVr9edbuCVUrk03yUPp-hs7ASQO+mEcLW5SzCWi8-ULog@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: SQL:2011 PERIODS vs Postgres Ranges? (David Steele <david@pgmasters.net>) |
Ответы |
Re: SQL:2011 PERIODS vs Postgres Ranges?
|
Список | pgsql-hackers |
On Sat, Mar 9, 2019 at 10:42 PM David Steele <david@pgmasters.net> wrote: > On 3/10/19 2:41 AM, Paul A Jungwirth wrote: > > I'm pretty far along > > with an add-on patch to create temporal *foreign* keys too, which I > > think should be part of this same bundle of work. Here is that patch. I've changed the title from "temporal_pks" to "temporal_fks" but it includes both. I've rebased on top of latest master, but also the patch assumes my other range_agg patch is already included. (I use range_agg to help implement the foreign key checks.) This patch is hopefully getting close, but I'd still call it a WIP. It has docs and tests, but it hasn't had any review yet (and neither has range_agg). Here are a few limitations: - It supports only range types, not SQL:2011 PERIODs. I'd like to add PERIODs too, but that seems like a major undertaking. I would probably need to partner with someone more experienced to get it done. Maybe it should be a separate CF entry. - The foreign keys support only NO ACTION and RESTRICT, not CASCADE/SET NULL/SET DEFAULT. The latter options are hard to implement now but would be trivial after adding UPDATE/DELETE FROM t FOR PORTION OF r FROM t1 TO t2, so I'm thinking that will be next on my list. :-) - I'm sure there are plenty of errors & infelicities people more knowledgeable than me can point out. Any feedback is gratefully welcomed. :-) Yours, Paul
Вложения
В списке pgsql-hackers по дате отправления: