Re: create table explicitly mention that unique|primary key constraint will create an

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, vignesh C <vignesh21(at)gmail(dot)com>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: create table explicitly mention that unique|primary key constraint will create an
Date: 2024-01-31 11:11:38
Message-ID: d7b210f3-bb44-4d73-a68a-f8eb51576c8f@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On 26.01.24 16:52, Laurenz Albe wrote:
> On Fri, 2024-01-26 at 19:01 +0530, vignesh C wrote:
>> CFBot shows that the patch does not apply anymore as in [1]:
>
> There was a conflict with 46a0cd4cefb.
> Updated version attached.

Sprinkled in some of David's suggestions, and pushed.

I was hesitant to burden the user with the difference between "relation"
and "table" at this point, so I took the former term out of the text.

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Laurenz Albe 2024-01-31 11:12:03 Re: SET ROLE versus SET SESSION AUTHORIZATION
Previous Message David G. Johnston 2024-01-30 20:49:42 Re: CREATE ROLE inheritance details