On Thu, Feb 15, 2018 at 11:06:27PM +, PG Doc comments form wrote:
> SELECT usename FROM pg_user;
>
> should be
> SELECT pg_user.usename FROM pg_user;
This is perfectly valid SQL. The column selected is assumed to be from
pg_user.
--
Michael
signature.asc
Description: PGP signature
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/8.0/static/user-manag.html
Description:
SELECT usename FROM pg_user;
should be
SELECT pg_user.usename FROM pg_user;
On 2018-02-15 1:47 PM, Tom Lane wrote:
=?utf-8?q?PG_Doc_comments_form?= writes:
See the example from the documentation for CREATE TABLE below. There should
be a comma before the CONSTRAINT keyword.
CREATE TABLE distributors (
did integer,
namevarchar(40)
CONSTRAINT con
=?utf-8?q?PG_Doc_comments_form?= writes:
> See the example from the documentation for CREATE TABLE below. There should
> be a comma before the CONSTRAINT keyword.
> CREATE TABLE distributors (
> did integer,
> namevarchar(40)
> CONSTRAINT con1 CHECK (did > 100 AND name <> '')
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/static/sql-createtable.html
Description:
See the example from the documentation for CREATE TABLE below. There should
be a comma before the CONSTRAINT keyword.
CREATE TABLE distributors (
Hello doc keepers,
There is a minor incorrect statement in the libpq docs at following page.
https://www.postgresql.org/docs/devel/static/libpq-exec.html
Where it mentions PG_DIAG_SQLSTATE, in the documentation of the
PQresultErrorField, it says ".. is always present". But as I found out, and
ve
