| From: | Pantelis Theodosiou <ypercube(at)gmail(dot)com> |
|---|---|
| To: | hans(at)matfyz(dot)cz, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: missing schema_name |
| Date: | 2021-03-01 15:29:02 |
| Message-ID: | CAE3TBxx44Y9_fNuOiBrgsoYq=sfFdyN2k1WWjap9SNHcqeP9nA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Mar 1, 2021 at 2:43 PM Pantelis Theodosiou <ypercube(at)gmail(dot)com>
wrote:
>
>
> On Mon, Mar 1, 2021 at 1:42 PM PG Doc comments form <
> noreply(at)postgresql(dot)org> wrote:
>
>> The following documentation comment has been logged on the website:
>>
>> Page: https://www.postgresql.org/docs/13/sql-createschema.html
>> Description:
>>
>> The second and forth syntax for CREATE SCHEMA is missing schema_name.
>>
>
> Right. It looks like the 2nd and 4th lines should be removed. The 1st and
> 3rd cover the syntax cases, don't they?
>
Oh, how silly of me. The command
CREATE SCHEMA AUTHORIZATION *role_specification*
creates a schema with same name as role_specification.
It is explained a few lines later:
*schema_name*
The name of a schema to be created. If this is omitted, the *user_name* is
used as the schema name.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Georgios Kokolatos | 2021-03-02 15:06:28 | Re: GROUP BY DISTINCT |
| Previous Message | Pantelis Theodosiou | 2021-03-01 14:43:38 | Re: missing schema_name |