[DOCS] 7.2. Table Expressions suggestion about NATURAL JOIN

http://www.postgresql.org/docs/9.0/static/queries-table-expressions.html http://www.postgresql.org/docs/9.0/static/sql-select.html Respectively: "Finally, NATURAL is a shorthand form of USING: it forms a USING list consisting of all column names that appear in both input tables. As with USING, th

Re: [DOCS] 7.2. Table Expressions suggestion about NATURAL JOIN

2011/5/18 Grzegorz Szpetkowski : > http://www.postgresql.org/docs/9.0/static/queries-table-expressions.html > http://www.postgresql.org/docs/9.0/static/sql-select.html > > Respectively: > > "Finally, NATURAL is a shorthand form of USING: it forms a USING list > consistin

[DOCS] 7.2. Table Expressions suggestion about NATURAL JOIN

http://www.postgresql.org/docs/9.0/static/queries-table-expressions.html http://www.postgresql.org/docs/9.0/static/sql-select.html Respectively: "Finally, NATURAL is a shorthand form of USING: it forms a USING list consisting of all column names that appear in both input tables. As with USING, th

[DOCS] 7.2. Table Expressions FULL join is only supported with merge-joinable join conditions

nable join conditions I mean add something like: "Note that you can't use such conditions with FULL JOIN, only equality of selected columns is supported with this type". Thanks, Grzegorz Szpetkowski -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your

[DOCS] 7.1. Overview (The SQL Language)

http://www.postgresql.org/docs/9.0/static/queries-overview.html "Assuming that there is a table called table1, this command would retrieve all rows and all columns from table1." Maybe it's worth adding: "Assuming that there is a table called table1, this command would retrieve all rows and all c

[DOCS] ALTER TABLE doc small thing

http://www.postgresql.org/docs/9.0/static/sql-altertable.html "To add a foreign key constraint to a table: ALTER TABLE distributors ADD CONSTRAINT distfk FOREIGN KEY (address) REFERENCES addresses (address) MATCH FULL;" This looks confusing to me. Is "MATCH FULL" works with non-composite (one ad

Re: [DOCS] ALTER TABLE doc small thing

then the effect is the same as if no were specified." I found that in SQL:2003 draft, so in above case MATCH FULL is syntactically ok, but rather confusing and effectively do nothing (maybe just impression purpose). Regards, G. Sz. 2011/5/9 Grzegorz Szpetkowski : > http://www.postgresql

[DOCS] 5.3.5. Foreign Keys (The SQL Language) possible enhance

, product_no integer REFERENCES products (product_no) NOT NULL, quantity integer ); Regards, Grzegorz Szpetkowski -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

[DOCS] Missing prefix unary '+' operator in Table 4-2 ?

not belong to "(any other)" group as: SELECT 5 ! + 6; ERROR: operator does not exist: integer ! integer LINE 1: SELECT 5 ! + 6; Regards, Grzegorz Szpetkowski -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

[DOCS] createuser/dropuser username

"user" LINE 1: ALTER ROLE user CREATEDB; ^ postgres=# ALTER ROLE "user" CREATEDB; ALTER ROLE Regards, Grzegorz Szpetkowski -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs

[DOCS] Default compression level for custom format in pg_dump ?

ion, 0 gives no compression at all (the input data is simply copied a block at a time). Z_DEFAULT_COMPRESSION requests a default compromise between speed and compression (currently equivalent to level 6)." #define Z_DEFAULT_COMPRESSION (-1) (zlib.h) What do you think about adding some clarification in Postgr