Re: SQL Property Graph Queries (SQL/PGQ)
Peter Eisentraut <peter@eisentraut.org>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix some typos and make small stylistic improvements
- 5282bf535e47 19 (unreleased) landed
-
Cleanup users and roles in graph_table_rls test
- 040a56be4bcc 19 (unreleased) landed
-
Dump labels in reproducible order
- c9babbc8816a 19 (unreleased) landed
-
SQL Property Graph Queries (SQL/PGQ)
- 2f094e7ac691 19 (unreleased) landed
-
Factor out constructSetOpTargetlist() from transformSetOperationTree()
- 8c2b30487cc7 19 (unreleased) landed
-
Sort out table_open vs. relation_open in rewriter
- d537f59fbbfc 19 (unreleased) landed
-
Rename grammar nonterminal to simplify reuse
- 8080f44f96a9 19 (unreleased) landed
-
Make ecpg parse.pl more robust with braces
- 7f88553ceaca 19 (unreleased) landed
-
Don't lock partitions pruned by initial pruning
- 525392d5727f 18.0 cited
-
Remove pg_regex_collation
- 792b2c7e6d92 18.0 cited
-
Use auxv to check for CRC32 instructions on ARM.
- aac831cafa6f 18.0 cited
-
Fix inappropriate uses of atol()
- f5a1311fccd2 18.0 cited
-
Remove unnecessary array object_classes[] in dependency.c
- ef5e2e90859a 17.0 cited
On 02.12.25 11:00, Ashutosh Bapat wrote: >> When you create future patches, consider using the git format-patch -v >> option. >> > I am still using timestamp as a version but passing it to -v instead > of treating it as a suffix. I like datestamp as versionstamp for the > reasons mentioned upthread. Date stamps are great, but why is there a hyphen between the "v" and the number? I have committed the parse.pl patch, mainly to test it out so that we don't have surprises later. (I had problems in the past making it work with older Perl versions, but things seems to have shifted forward now.) It can live on its own, I think. It looks like undirected matching -[ ]- (without arrows) doesn't work correctly. It seems to just match in one direction. I don't see any tests. Is this implemented? Also, make sure the role names in graph_table_rls.sql start with regress_: CREATE USER graph_rls_alice NOLOGIN; +WARNING: roles created by regression test cases should have names starting with "regress_" (This is the FreeBSD CI failure.)