pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra
7+ messages / 1 participants
[nested] [flat]

* pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra
@ 2020-12-08 18:10  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 7+ messages in thread

From: Tom Lane @ 2020-12-08 18:10 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Doc: clarify that CREATE TABLE discards redundant unique constraints.

The SQL standard says that redundant unique constraints are disallowed,
but we long ago decided that throwing an error would be too
user-unfriendly, so we just drop redundant ones.  The docs weren't very
clear about that though, as this behavior was only explained for PRIMARY
KEY vs UNIQUE, not UNIQUE vs UNIQUE.

While here, I couldn't resist doing some copy-editing and markup-fixing
on the adjacent text about INCLUDE options.

Per bug #16767 from Matthias vd Meent.

Discussion: https://postgr.es/m/16767-1714a2056ca516d0@postgresql.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f2a69b352de1dffc534c4835010e736018aa94de

Modified Files
--------------
doc/src/sgml/ref/create_table.sgml | 58 +++++++++++++++++++++++---------------
1 file changed, 36 insertions(+), 22 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra
@ 2020-12-08 18:10  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 7+ messages in thread

From: Tom Lane @ 2020-12-08 18:10 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Doc: clarify that CREATE TABLE discards redundant unique constraints.

The SQL standard says that redundant unique constraints are disallowed,
but we long ago decided that throwing an error would be too
user-unfriendly, so we just drop redundant ones.  The docs weren't very
clear about that though, as this behavior was only explained for PRIMARY
KEY vs UNIQUE, not UNIQUE vs UNIQUE.

While here, I couldn't resist doing some copy-editing and markup-fixing
on the adjacent text about INCLUDE options.

Per bug #16767 from Matthias vd Meent.

Discussion: https://postgr.es/m/16767-1714a2056ca516d0@postgresql.org

Branch
------
REL_10_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/567d6d1ff6173cae02a4b89b4283137bf56caf97

Modified Files
--------------
doc/src/sgml/ref/create_table.sgml | 22 +++++++++++++++-------
1 file changed, 15 insertions(+), 7 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra
@ 2020-12-08 18:10  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 7+ messages in thread

From: Tom Lane @ 2020-12-08 18:10 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Doc: clarify that CREATE TABLE discards redundant unique constraints.

The SQL standard says that redundant unique constraints are disallowed,
but we long ago decided that throwing an error would be too
user-unfriendly, so we just drop redundant ones.  The docs weren't very
clear about that though, as this behavior was only explained for PRIMARY
KEY vs UNIQUE, not UNIQUE vs UNIQUE.

While here, I couldn't resist doing some copy-editing and markup-fixing
on the adjacent text about INCLUDE options.

Per bug #16767 from Matthias vd Meent.

Discussion: https://postgr.es/m/16767-1714a2056ca516d0@postgresql.org

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/5303706b320864332abd99b666a466863ffece22

Modified Files
--------------
doc/src/sgml/ref/create_table.sgml | 58 +++++++++++++++++++++++---------------
1 file changed, 36 insertions(+), 22 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra
@ 2020-12-08 18:10  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 7+ messages in thread

From: Tom Lane @ 2020-12-08 18:10 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Doc: clarify that CREATE TABLE discards redundant unique constraints.

The SQL standard says that redundant unique constraints are disallowed,
but we long ago decided that throwing an error would be too
user-unfriendly, so we just drop redundant ones.  The docs weren't very
clear about that though, as this behavior was only explained for PRIMARY
KEY vs UNIQUE, not UNIQUE vs UNIQUE.

While here, I couldn't resist doing some copy-editing and markup-fixing
on the adjacent text about INCLUDE options.

Per bug #16767 from Matthias vd Meent.

Discussion: https://postgr.es/m/16767-1714a2056ca516d0@postgresql.org

Branch
------
REL9_6_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/2bf5d1a74a33ed45939ed4c16054aee51ab65540

Modified Files
--------------
doc/src/sgml/ref/create_table.sgml | 22 +++++++++++++++-------
1 file changed, 15 insertions(+), 7 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra
@ 2020-12-08 18:10  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 7+ messages in thread

From: Tom Lane @ 2020-12-08 18:10 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Doc: clarify that CREATE TABLE discards redundant unique constraints.

The SQL standard says that redundant unique constraints are disallowed,
but we long ago decided that throwing an error would be too
user-unfriendly, so we just drop redundant ones.  The docs weren't very
clear about that though, as this behavior was only explained for PRIMARY
KEY vs UNIQUE, not UNIQUE vs UNIQUE.

While here, I couldn't resist doing some copy-editing and markup-fixing
on the adjacent text about INCLUDE options.

Per bug #16767 from Matthias vd Meent.

Discussion: https://postgr.es/m/16767-1714a2056ca516d0@postgresql.org

Branch
------
REL9_5_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/14db9579222138b3fba2f73c285ff3f9e4bf9465

Modified Files
--------------
doc/src/sgml/ref/create_table.sgml | 22 +++++++++++++++-------
1 file changed, 15 insertions(+), 7 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra
@ 2020-12-08 18:10  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 7+ messages in thread

From: Tom Lane @ 2020-12-08 18:10 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Doc: clarify that CREATE TABLE discards redundant unique constraints.

The SQL standard says that redundant unique constraints are disallowed,
but we long ago decided that throwing an error would be too
user-unfriendly, so we just drop redundant ones.  The docs weren't very
clear about that though, as this behavior was only explained for PRIMARY
KEY vs UNIQUE, not UNIQUE vs UNIQUE.

While here, I couldn't resist doing some copy-editing and markup-fixing
on the adjacent text about INCLUDE options.

Per bug #16767 from Matthias vd Meent.

Discussion: https://postgr.es/m/16767-1714a2056ca516d0@postgresql.org

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/c6f8d17d04d1bf1ddcbe0f2293d8f1462a1379f4

Modified Files
--------------
doc/src/sgml/ref/create_table.sgml | 58 +++++++++++++++++++++++---------------
1 file changed, 36 insertions(+), 22 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra
@ 2020-12-08 18:10  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 7+ messages in thread

From: Tom Lane @ 2020-12-08 18:10 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Doc: clarify that CREATE TABLE discards redundant unique constraints.

The SQL standard says that redundant unique constraints are disallowed,
but we long ago decided that throwing an error would be too
user-unfriendly, so we just drop redundant ones.  The docs weren't very
clear about that though, as this behavior was only explained for PRIMARY
KEY vs UNIQUE, not UNIQUE vs UNIQUE.

While here, I couldn't resist doing some copy-editing and markup-fixing
on the adjacent text about INCLUDE options.

Per bug #16767 from Matthias vd Meent.

Discussion: https://postgr.es/m/16767-1714a2056ca516d0@postgresql.org

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/e824ddc37f3c57a52eec0d56131c4949cd66220c

Modified Files
--------------
doc/src/sgml/ref/create_table.sgml | 58 +++++++++++++++++++++++---------------
1 file changed, 36 insertions(+), 22 deletions(-)



^ permalink  raw  reply  [nested|flat] 7+ messages in thread


end of thread, other threads:[~2020-12-08 18:10 UTC | newest]

Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-12-08 18:10 pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra Tom Lane <tgl@sss.pgh.pa.us>
2020-12-08 18:10 pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra Tom Lane <tgl@sss.pgh.pa.us>
2020-12-08 18:10 pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra Tom Lane <tgl@sss.pgh.pa.us>
2020-12-08 18:10 pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra Tom Lane <tgl@sss.pgh.pa.us>
2020-12-08 18:10 pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra Tom Lane <tgl@sss.pgh.pa.us>
2020-12-08 18:10 pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra Tom Lane <tgl@sss.pgh.pa.us>
2020-12-08 18:10 pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox