Re: Add Boolean node
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-12-30T08:58:10Z
Lists: pgsql-hackers
On 29.12.21 21:32, Andres Freund wrote: > On 2021-12-27 09:53:32 -0500, Tom Lane wrote: >> Didn't really read the patch in any detail, but I did have one idea: >> I think that the different things-that-used-to-be-Value-nodes ought to >> use different field names, say ival, rval, bval, sval not just "val". >> That makes it more likely that you'd catch any code that is doing the >> wrong thing and not going through one of the access macros. > > If we go around changing all these places, it might be worth to also change > Integer to be a int64 instead of an int. I was actually looking into that, when I realized that most uses of Integer were actually Booleans. Hence the current patch to clear those fake Integers out of the way. I haven't gotten to analyze the int64 question any further, but it should be easier hereafter.
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add Boolean node
- 941460fcf731 15.0 landed
-
Rename value node fields
- c4cc2850f4d1 15.0 landed
-
Refactor AlterRole()
- 93415a3b5ac8 15.0 landed