Re: 'converts internal representation to "..."' comment is confusing
Steve Chavez <steve@supabase.io>
From: Steve Chavez <steve@supabase.io>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2023-05-15T02:50:45Z
Lists: pgsql-hackers
Thanks a lot for the clarification! The "..." looks enigmatic right now. I think cstring would save newcomers some head-scratching. Open to suggestions though. Best regards, Steve On Sun, 14 May 2023 at 22:36, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Steve Chavez <steve@supabase.io> writes: > > I found "..." confusing in some comments, so this patch changes it to > > "cstring". Which seems to be the intention after all. > > Those comments are Berkeley-era, making them probably a decade older > than the "cstring" pseudotype (invented in b663f3443). Perhaps what > you suggest is an improvement, but I'm not sure that appealing to > original intent can make the case. > > regards, tom lane >
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Change "..." to cstring in old input/output function comments.
- b491a15f8c14 16.0 landed