| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: createuser --memeber and PG 16 |
| Date: | 2023-05-11 14:07:23 |
| Message-ID: | CA+Tgmob6euOYrg0h10EG3yFPMSU=DhiDAepvgD=E1egLOLHfSQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 10, 2023 at 1:33 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> This seems like it will be forever confusing to people. I frankly don't
> know why --role matching CREATE ROLE ... ROLE IN was not already
> confusing in pre-PG 16. Any new ideas for improvement?
Yeah, it's a bad situation. I think --role is basically misnamed.
Something like --add-to-group would have been clearer, but that also
has the problem of being inconsistent with the SQL command. The whole
ROLE vs. IN ROLE thing is inherently quite confusing, I think. It's
very easy to get confused about which direction the membership arrows
are pointing.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-05-11 14:14:54 | Re: v16 regression - wrong query results with LEFT JOINs + join removal |
| Previous Message | Joel Jacobson | 2023-05-11 14:03:33 | Should CSV parsing be stricter about mid-field quotes? |