Re: PERIOD foreign key feature - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: PERIOD foreign key feature
Date
Msg-id ZjuPwWh7JWDnHR5J@momjian.us
Whole thread Raw
In response to Re: PERIOD foreign key feature  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: PERIOD foreign key feature
List pgsql-hackers
On Wed, May  8, 2024 at 02:29:34PM +0200, Peter Eisentraut wrote:
> > > Finally, if the foreign key has a PERIOD column_name specification
> > > the corresponding refcolumn, if present, must also be marked
> > > PERIOD.  If the refcolumn clause is omitted, and thus the reftable's
> > > primary key constraint chosen, the primary key must have its final
> > > column marked WITHOUT OVERLAPS.
> > 
> > Yes, David is correct here on all points. I like his suggestion to
> > clarify the language here also. If you need a patch from me let me know,
> > but I assume it's something a committer can just make happen?
> 
> In principle yes, but it's also very helpful if someone produces an actual
> patch file, with complete commit message, credits, mailing list link, etc.

I am ready to do the work, but waited a day for Peter to reply, since he
was the author of the text.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.



pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Re: CREATE DATABASE with filesystem cloning
Next
From: Tom Lane
Date:
Subject: Re: Trigger violates foreign key constraint