Horton
Menu

Re: Fix DROP PROPERTY GRAPH "unsupported object class" error

Michael Paquier <michael@paquier.xyz>

View thread
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, Alex Guo <guo.alex.hengchen@gmail.com>, Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2026-06-10T01:18:40Z
Lists: pgsql-hackers 
On Mon, Jun 08, 2026 at 02:43:22PM -0400, Tom Lane wrote:
> The argument that these only need to be machine-readable doesn't sway
> me a lot.  In the end, any code that is disassembling these strings is
> going to be written by a human, and the human is a lot more likely to
> make a mistake about which identifier is which if they're not labeled.

+1.  I'm not a robot yet and I still want to be able to parse these
strings by reading them.  As things stand, this code does not allow
one to understand what each sub-object refers to.  We are still in
beta, let's improve the situation.
--
Michael

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Readable identity strings for property graph objects

  2. Handle element label and label property objects in object address functions

  3. Simplify code in objectaddress.c for some property graph objects