| From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Junwang Zhao <zhjwpku(at)gmail(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, Vik Fearing <vik(at)postgresfriends(dot)org>, Ajay Pal <ajay(dot)pal(dot)k(at)gmail(dot)com>, Imran Zaheer <imran(dot)zhir(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SQL Property Graph Queries (SQL/PGQ) |
| Date: | 2025-12-02 06:56:15 |
| Message-ID: | CAExHW5sT4u0OGf0Ckx63XHUnyMYsbBKnoGpNVPK6+WNS58BCPw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 25, 2025 at 7:28 PM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> On 20.11.25 16:00, Ashutosh Bapat wrote:
> >> 5.
> >>
> >> src/backend/catalog/sql_features.txt
> >>
> >> +G034 Path concatenation YES SQL/PGQ required
> >>
> >> Do we support path concatenation?
> > I don't think so. But let Peter confirm it.
>
> AFAICT, path concatenation just allows that you can write multiple
> element patterns in a row, like ()-[]->(). I don't see how it could
> make sense to not support that.
Ah! I confused path concatenation with either path pattern list or
path pattern multiset alternation. Sorry.
--
Best Wishes,
Ashutosh Bapat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2025-12-02 07:08:01 | Re: Proposal: Conflict log history table for Logical Replication |
| Previous Message | Kirill Reshke | 2025-12-02 06:37:08 | Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect |