Re: SQL Property Graph Queries (SQL/PGQ) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: SQL Property Graph Queries (SQL/PGQ)
Date
Msg-id 3c0f5c31-9a89-42ba-a53d-9d9148885297@eisentraut.org
Whole thread Raw
In response to Re: SQL Property Graph Queries (SQL/PGQ)  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Responses Re: SQL Property Graph Queries (SQL/PGQ)
List pgsql-hackers
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.)




pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: unifying error messages
Next
From: Bryan Green
Date:
Subject: Re: [PATCH] Allow complex data for GUC extra.