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

From Ashutosh Bapat
Subject Re: SQL Property Graph Queries (SQL/PGQ)
Date
Msg-id CAExHW5uQAiB7OrYbr=tzpdjA3R-zrqPAr_rZ2wa+nvV32xk9fg@mail.gmail.com
Whole thread
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 Fri, Feb 27, 2026 at 2:14 PM Ashutosh Bapat
<ashutosh.bapat.oss@gmail.com> wrote:
> >
> > Except, this error message change
> >
> > -ERROR:  property "ename" of element variable "src" not found
> > +ERROR:  none of the property graph elements associated with variable
> > "src" have property with name "ename" defined
> >
> > I don't know, that seems quite a complicated message for such a simple
> > mistake.  Also, properties are associated with labels, not with graph
> > elements, so this seems misleading.
> >
>
> Hmm, mentioning labels was getting even more complicated, so I had to drop it.
>
> How about the earlier version with "of" replaced with "for"? "property
> "ename" for element variable "src" not found. The users can lookup the
> labels associated with variable src and figure out what went wrong
> themselves? I want to avoid simplistic error that other products give
> like "property "ename" not found" since it does not clarify whether
> the property is absent in the property graph or is not associated with
> labels in the pattern.

Here's a patchset with all the earlier patches squashed into 0001.
0002 is changing this specific error message as described in the para
above. Please let me know if you have any other suggestions.

--
Best Wishes,
Ashutosh Bapat

Attachment

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: doc: Clarify that empty COMMENT string removes the comment
Next
From: Andres Freund
Date:
Subject: Re: Release postmaster working memory context in slotsync worker