rdelaage/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-10-04 23:06:52 +02:00
Code Issues Packages Projects Releases Wiki Activity
d4ede668d6
postgresql/doc/src/sgml/ref/drop_group.sgml

54 lines
1.0 KiB
Plaintext
Raw Normal View History

* User management commands no longer user pg_exec_query_dest -> more robust * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
2000-01-14 23:11:38 +01:00
<!--
Remove cvs keywords from all files.
2010-09-20 22:08:53 +02:00
doc/src/sgml/ref/drop_group.sgml
Use PostgreSQL consistantly throughout docs. Before, usage was split evenly between Postgres and PostgreSQL.
2001-12-08 04:24:40 +01:00
PostgreSQL documentation
* User management commands no longer user pg_exec_query_dest -> more robust * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
2000-01-14 23:11:38 +01:00
-->
<refentry id="SQL-DROPGROUP">
doc: Improve DocBook XML validity DocBook XML is superficially compatible with DocBook SGML but has a slightly stricter DTD that we have been violating in a few cases. Although XSLT doesn't care whether the document is valid, the style sheets don't necessarily process invalid documents correctly, so we need to work toward fixing this. This first commit moves the indexterms in refentry elements to an allowed position. It has no impact on the output.
2014-02-24 03:25:35 +01:00
<indexterm zone="sql-dropgroup">
<primary>DROP GROUP</primary>
</indexterm>
* User management commands no longer user pg_exec_query_dest -> more robust * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
2000-01-14 23:11:38 +01:00
<refmeta>
Remove unnecessary xref endterm attributes and title ids The endterm attribute is mainly useful when the toolchain does not support automatic link target text generation for a particular situation. In the past, this was required by the man page tools for all reference page links, but that is no longer the case, and it now actually gets in the way of proper automatic link text generation. The only remaining use cases are currently xrefs to refsects.
2010-04-03 09:23:02 +02:00
<refentrytitle>DROP GROUP</refentrytitle>
Set SQL man pages to be section 7 by default, and only transform them to another section if required by the platform (instead of the old way of building them in section "l" and always transforming them to the platform-specific section). This speeds up the installation on common platforms, and it avoids some funny business with the man page tools and build process.
2008-11-14 11:22:48 +01:00
<manvolnum>7</manvolnum>
* User management commands no longer user pg_exec_query_dest -> more robust * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
2000-01-14 23:11:38 +01:00
<refmiscinfo>SQL - Language Statements</refmiscinfo>
</refmeta>
Last round of reference page editing.
2003-05-04 04:23:16 +02:00
* User management commands no longer user pg_exec_query_dest -> more robust * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
2000-01-14 23:11:38 +01:00
<refnamediv>
Last round of reference page editing.
2003-05-04 04:23:16 +02:00
<refname>DROP GROUP</refname>
Basic documentation for ROLEs. The user-manag chapter still needs to be rewritten, but at least the reference pages are reasonably sane.
2005-07-27 01:24:02 +02:00
<refpurpose>remove a database role</refpurpose>
* User management commands no longer user pg_exec_query_dest -> more robust * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
2000-01-14 23:11:38 +01:00
</refnamediv>
Last round of reference page editing.
2003-05-04 04:23:16 +02:00
* User management commands no longer user pg_exec_query_dest -> more robust * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
2000-01-14 23:11:38 +01:00
<refsynopsisdiv>
Last round of reference page editing.
2003-05-04 04:23:16 +02:00
<synopsis>
DROP IF EXISTS for ROLE/USER/GROUP
2006-02-04 20:06:47 +01:00
DROP GROUP [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable> [, ...]
Last round of reference page editing.
2003-05-04 04:23:16 +02:00
</synopsis>
* User management commands no longer user pg_exec_query_dest -> more robust * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
2000-01-14 23:11:38 +01:00
</refsynopsisdiv>
Last round of reference page editing.
2003-05-04 04:23:16 +02:00
<refsect1>
<title>Description</title>
* User management commands no longer user pg_exec_query_dest -> more robust * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
2000-01-14 23:11:38 +01:00
<para>
Basic documentation for ROLEs. The user-manag chapter still needs to be rewritten, but at least the reference pages are reasonably sane.
2005-07-27 01:24:02 +02:00
<command>DROP GROUP</command> is now an alias for
Remove unnecessary xref endterm attributes and title ids The endterm attribute is mainly useful when the toolchain does not support automatic link target text generation for a particular situation. In the past, this was required by the man page tools for all reference page links, but that is no longer the case, and it now actually gets in the way of proper automatic link text generation. The only remaining use cases are currently xrefs to refsects.
2010-04-03 09:23:02 +02:00
<xref linkend="sql-droprole">.
* User management commands no longer user pg_exec_query_dest -> more robust * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
2000-01-14 23:11:38 +01:00
</para>
</refsect1>
Last round of reference page editing.
2003-05-04 04:23:16 +02:00
<refsect1>
<title>Compatibility</title>
<para>
There is no <command>DROP GROUP</command> statement in the SQL standard.
</para>
* User management commands no longer user pg_exec_query_dest -> more robust * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
2000-01-14 23:11:38 +01:00
</refsect1>
Last round of reference page editing.
2003-05-04 04:23:16 +02:00
<refsect1>
<title>See Also</title>
<simplelist type="inline">
Remove unnecessary xref endterm attributes and title ids The endterm attribute is mainly useful when the toolchain does not support automatic link target text generation for a particular situation. In the past, this was required by the man page tools for all reference page links, but that is no longer the case, and it now actually gets in the way of proper automatic link text generation. The only remaining use cases are currently xrefs to refsects.
2010-04-03 09:23:02 +02:00
<member><xref linkend="sql-droprole"></member>
Last round of reference page editing.
2003-05-04 04:23:16 +02:00
</simplelist>
</refsect1>
* User management commands no longer user pg_exec_query_dest -> more robust * Let unprivileged users change their own passwords. * The password is now an Sconst in the parser, which better reflects its text datatype and also forces users to quote them. * If your password is NULL you won't be written to the password file, meaning you can't connect until you have a password set up (if you use password authentication). * When you drop a user that owns a database you get an error. The database is not gone.
2000-01-14 23:11:38 +01:00
</refentry>
Reference in New Issue Copy Permalink