From: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Sameer Thakur <samthakur74(at)gmail(dot)com>, PostgreSQL Mailing Lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Extra functionality to createuser |
Date: | 2013-11-20 16:23:38 |
Message-ID: | CAFNqd5XmasFZmUpLx56Otch4OdH60SED7we5vEfbAGd_iqjf0g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Wait, that doesn't work if more than one role is added, as they get
merged together by the quoting.
A somewhat ugly amount of quoting can be done at the shell level to
induce double quotes.
$ createuser -g "\"test_rol'e_3\"" usequoted3
I note that similar (with not quite identical behaviour) issues apply
to the user name. Perhaps the
resolution to this is to leave quoting issues to the administrator.
That simplifies the problem away.
I suspect that the apparatus needed to do a thorough solution (e.g. -
parse the string, and do something
"smarter") may be larger than is worth getting into.
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2013-11-20 16:25:56 | Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 |
Previous Message | Hannu Krosing | 2013-11-20 16:22:21 | Re: additional json functionality |