Re: SQL:2011 application time
Paul A Jungwirth <pj@illuminatedcomputing.com>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Rename gist stratnum support function
- 32edf732e8dc 18.0 landed
-
Remove support for temporal RESTRICT foreign keys
- b83e8a2ca2eb 18.0 landed
-
Cache NO ACTION foreign keys separately from RESTRICT foreign keys
- 9926f854d077 18.0 landed
-
Fix NO ACTION temporal foreign keys when the referenced endpoints change
- 1772d554b089 18.0 landed
-
Improve whitespace in without_overlaps test
- 888d4523f0c2 18.0 landed
-
Tests for logical replication with temporal keys
- 939b0908c87a 18.0 landed
-
Support for GiST in get_equal_strategy_number()
- 74edabce7a33 18.0 landed
-
Make the conditions in IsIndexUsableForReplicaIdentityFull() more explicit
- 13544e790ef8 18.0 landed
-
Replace get_equal_strategy_number_for_am() by get_equal_strategy_number()
- a2a475b011cf 18.0 landed
-
Improve internal logical replication error for missing equality strategy
- 321c287351f7 18.0 landed
-
Simplify IsIndexUsableForReplicaIdentityFull()
- 7727049e8f66 18.0 landed
-
Fix ALTER TABLE / REPLICA IDENTITY for temporal tables
- 79b575d3bc09 18.0 landed
-
doc: Update pg_constraint.conexclop docs for WITHOUT OVERLAPS
- f683ba0867da 18.0 landed
-
doc: Add PERIOD to ALTER TABLE reference docs
- d56af4c882e2 18.0 landed
-
doc: Add WITHOUT OVERLAPS to ALTER TABLE reference docs
- bf621059500b 18.0 landed
-
Add temporal FOREIGN KEY contraints
- 89f908a6d0ac 18.0 landed
- 34768ee36165 17.0 landed
-
Add temporal PRIMARY KEY and UNIQUE constraints
- fc0438b4e805 18.0 landed
- 46a0cd4cefb4 17.0 landed
-
Add stratnum GiST support function
- 7406ab623fee 18.0 landed
- 6db4598fcb82 17.0 landed
-
Avoid crashing when a JIT-inlined backend function throws an error.
- 5d6c64d29097 17.0 cited
-
Revert temporal primary keys and foreign keys
- 8aee330af55d 17.0 landed
-
Fix ON CONFLICT DO NOTHING/UPDATE for temporal indexes
- 144c2ce0cc75 17.0 landed
-
Add test for REPLICA IDENTITY with a temporal key
- 482e108cd38d 17.0 landed
-
Use half-open interval notation in without_overlaps tests
- 5577a71fb0cc 17.0 landed
-
Use daterange and YMD in without_overlaps tests instead of tsrange.
- a88c800deb6f 17.0 landed
-
Rename pg_constraint.conwithoutoverlaps to conperiod
- 030e10ff1a36 17.0 landed
-
Fix comment on gist_stratnum_btree
- 86232a49a437 17.0 landed
-
Add missing TAP test name
- 1ab763fc22ad 16.0 cited
-
Improve error handling of HMAC computations
- 5513dc6a304d 15.0 cited
-
Rename functions to avoid future conflicts
- ee419607381d 15.0 landed
Attachments
- v16-0001-Add-temporal-PRIMARY-KEY-and-UNIQUE-constraints.patch (text/x-patch) patch v16-0001
- v16-0002-Add-temporal-FOREIGN-KEYs.patch (text/x-patch) patch v16-0002
- v16-0003-Add-UPDATE-DELETE-FOR-PORTION-OF.patch (text/x-patch) patch v16-0003
- v16-0004-Add-CASCADE-SET-NULL-SET-DEFAULT-for-temporal-fo.patch (text/x-patch) patch v16-0004
- v16-0005-Add-PERIODs.patch (text/x-patch) patch v16-0005
On 9/24/23 21:52, jian he wrote:
> On Wed, Sep 20, 2023 at 10:50 AM Paul Jungwirth
> <pj@illuminatedcomputing.com> wrote:
>>
>> On 9/17/23 20:11, jian he wrote:
>>> small issues so far I found, v14.
>>
>> Thank you again for the review! v15 is attached.
>>
>
> hi. some tiny issues.
Rebased v16 patches attached.
> IN src/backend/utils/adt/ri_triggers.c
>
> else {
> appendStringInfo(&querybuf, "SELECT 1 FROM %s%s x",
> pk_only, pkrelname);
> }
> should change to
>
> else
> {
> appendStringInfo(&querybuf, "SELECT 1 FROM %s%s x",
> pk_only, pkrelname);
> }
Fixed.
> It would be better, we mention it somewhere:
> by default, you can only have a primary key(range_type[...],
> range_type WITHOUT OVERLAPS).
>
> preceding without overlaps, all columns (in primary key) data types
> only allowed range types.
> -------------------------------
> The WITHOUT OVERLAPS value must be a range type and is used to
> constrain the record's applicability to just that interval (usually a
> range of dates or timestamps).
>
> "interval", I think "period" or "range" would be better. I am not sure
> we need to mention " must be a range type, not a multi range type".
I reworked those two paragraphs to incorporate those suggestions and
hopefully clarify the idea bit further. (I'll revise these again once I
support multiple WITHOUT OVERLAPS columns.)
> I just `git apply`, then ran the test, and one test failed. Some minor
> changes need to make the test pass.
I couldn't reproduce this. If you're still seeing a failure please let
me know what you're seeing.
These patches also fix a problem I found with FKs when used with
btree_gist. Privately I'm using the script below [1] to re-run all my
tests with that extension and int+range columns. I'd like to add
something similar to contrib/btree_gist. I'm open to advice how best to
do that if anyone has any!
[1] #!/bin/bash
set -eu
# without_overlaps
cat ../src/test/regress/sql/without_overlaps.sql | \
sed -E 's/int4range/integer/g' | \
sed -E 's/valid_at integer/valid_at int4range/' | \
sed -E 's/int8range/bigint/g' | \
sed -E 's/'"'"'\[(-?[[:digit:]]+),\1\]'"'"'/\1/g' | \
cat > ./sql/without_overlaps.sql
cat ../src/test/regress/expected/without_overlaps.out | \
sed -E 's/int4range/integer/g' | \
sed -E 's/valid_at integer/valid_at int4range/' | \
sed -E 's/incompatible types: integer and tsrange/incompatible types:
int4range and tsrange/' | \
sed -E 's/int8range/bigint/g' | \
sed -E 's/'"'"'\[(-?[[:digit:]]+),\1\]'"'"'/\1/g' | \
sed -E 's/'"'"'\[(-?[[:digit:]]+),-?[[:digit:]]+\)'"'"'/\1/g' | \
sed -E 's/\[(-?[[:digit:]]+),\1\]/\1/g' | \
sed -E 's/\[(-?[[:digit:]]+),-?[[:digit:]]+\)/\1/g' | \
sed -E 'N;P;s/^ +id [^\n]+\n-+(\+.*)$/----\1/p;D' | \
sed -E
's/^----------\+-----------\+-----------\+----------\+---------$/----------+---------+-----------+----------+---------/'
| \
sed -E
's/^----\+-------------------------\+--------\+-------$/----+-------------------------+-----+-------/'
| \
cat > ./expected/without_overlaps.out
# for_portion_of
cat ../src/test/regress/sql/for_portion_of.sql | \
sed -E 's/int4range/integer/g' | \
sed -E 's/valid_at integer/valid_at int4range/' | \
sed -E 's/'"'"'\[(-?[[:digit:]]+),\1\]'"'"'/\1/g' | \
cat > ./sql/for_portion_of.sql
cat ../src/test/regress/expected/for_portion_of.out | \
sed -E 's/int4range/integer/g' | \
sed -E 's/valid_at integer/valid_at int4range/' | \
sed -E 's/'"'"'\[(-?[[:digit:]]+),\1\]'"'"'/\1/g' | \
sed -E 's/'"'"'\[(-?[[:digit:]]+),-?[[:digit:]]+\)'"'"'/\1/g' | \
sed -E 's/\[(-?[[:digit:]]+),\1\]/\1/g' | \
sed -E 's/\[(-?[[:digit:]]+),-?[[:digit:]]+\)/\1/g' | \
sed -E 'N;P;s/^ +id [^\n]+\n-+(\+.*)$/----\1/p;D' | \
cat > ./expected/for_portion_of.out
Regards,
--
Paul ~{:-)
pj@illuminatedcomputing.com