Thread

Commits

  1. Remove inbound links to sql-createuser

  1. Remove inbound links to sql-createuser

    David G. Johnston <david.g.johnston@gmail.com> — 2017-10-30T20:31:44Z

    Since CREATE USER is officially an alias for CREATE ROLE other parts of the
    documentation should point to CREATE ROLE, not CREATE USER.  Most do but I
    noticed when looking at CREATE DATABASE that it did not.  Further searching
    turned up the usage in client-auth.sgml.  That one is questionable since we
    are indeed talking about LOGIN roles there but we are already pointing to
    sql-alterrole instead of sql-alteruser and so changing the create variation
    to point to sql-createrole seems warranted.
    
    Attached, and below.
    
    David J.
    
    diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
    index 722f3da813..99921ba079 100644
    --- a/doc/src/sgml/client-auth.sgml
    +++ b/doc/src/sgml/client-auth.sgml
    @@ -998,9 +998,9 @@ omicron         bryanh                  guest1
         separate from operating system user passwords. The password for
         each database user is stored in the <literal>pg_authid</literal> system
         catalog. Passwords can be managed with the SQL commands
    -    <xref linkend="sql-createuser"> and
    +    <xref linkend="sql-createrole"> and
         <xref linkend="sql-alterrole">,
    -    e.g., <userinput>CREATE USER foo WITH PASSWORD 'secret'</userinput>,
    +    e.g., <userinput>CREATE ROLE foo WITH LOGIN PASSWORD
    'secret'</userinput>,
         or the <application>psql</application>
         command <literal>\password</literal>.
         If no password has been set up for a user, the stored password
    diff --git a/doc/src/sgml/ref/create_database.sgml
    b/doc/src/sgml/ref/create_database.sgml
    index 3e35c776ea..f63f1f92ac 100644
    --- a/doc/src/sgml/ref/create_database.sgml
    +++ b/doc/src/sgml/ref/create_database.sgml
    @@ -45,7 +45,7 @@ CREATE DATABASE <replaceable
    class="parameter">name</replaceable>
       <para>
        To create a database, you must be a superuser or have the special
        <literal>CREATEDB</literal> privilege.
    -   See <xref linkend="sql-createuser">.
    +   See <xref linkend="sql-createrole">.
       </para>
    
       <para>
    
  2. Re: Remove inbound links to sql-createuser

    Stephen Frost <sfrost@snowman.net> — 2017-10-31T12:27:02Z

    David,
    
    * David G. Johnston (david.g.johnston@gmail.com) wrote:
    > Since CREATE USER is officially an alias for CREATE ROLE other parts of the
    > documentation should point to CREATE ROLE, not CREATE USER.  Most do but I
    > noticed when looking at CREATE DATABASE that it did not.  Further searching
    > turned up the usage in client-auth.sgml.  That one is questionable since we
    > are indeed talking about LOGIN roles there but we are already pointing to
    > sql-alterrole instead of sql-alteruser and so changing the create variation
    > to point to sql-createrole seems warranted.
    
    +1.
    
    Barring objections, I'll commit this in a bit.
    
    Thanks!
    
    Stephen
    
  3. Re: Remove inbound links to sql-createuser

    Stephen Frost <sfrost@snowman.net> — 2017-10-31T18:06:19Z

    David,
    
    * Stephen Frost (sfrost@snowman.net) wrote:
    > * David G. Johnston (david.g.johnston@gmail.com) wrote:
    > > Since CREATE USER is officially an alias for CREATE ROLE other parts of the
    > > documentation should point to CREATE ROLE, not CREATE USER.  Most do but I
    > > noticed when looking at CREATE DATABASE that it did not.  Further searching
    > > turned up the usage in client-auth.sgml.  That one is questionable since we
    > > are indeed talking about LOGIN roles there but we are already pointing to
    > > sql-alterrole instead of sql-alteruser and so changing the create variation
    > > to point to sql-createrole seems warranted.
    > 
    > +1.
    > 
    > Barring objections, I'll commit this in a bit.
    
    Pushed to master, with a small bit of word-smithing in the CREATE ROLE
    docs also.
    
    Thanks!
    
    Stephen