You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Rename pg_constraint.conwithoutoverlaps to conperiod
pg_constraint.conwithoutoverlaps was recently added to support primarykeys and unique constraints with the WITHOUT OVERLAPS clause. Anupcoming patch provides the foreign-key side of this functionality,but the syntax there is different and uses the keyword PERIOD. Itwould make sense to use the same pg_constraint field for both ofthese, but then we should pick a more general name that conveys "thisconstraint has a temporal/period-related feature". conperiod worksfor that and is nicely compact. Changing this now avoids possiblyhaving to introduce versioning into clients. Note there are stillsome "without overlaps" variables left, which deal specifically withthe parsing of the primary key/unique constraint feature.Author: Paul A. Jungwirth <pj@illuminatedcomputing.com>Discussion:https://www.postgresql.org/message-id/flat/CA+renyUApHgSZF9-nd-a0+OPGharLQLO=mDHcY4_qQ0+noCUVg@mail.gmail.com