Re: cataloguing NOT NULL constraints
От | Robert Haas |
---|---|
Тема | Re: cataloguing NOT NULL constraints |
Дата | |
Msg-id | CA+TgmoaFLgpVHzDGeY=9gSk1qxK-mf-r3QRdC22eBzzShJ5uCA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: cataloguing NOT NULL constraints (Isaac Morland <isaac.morland@gmail.com>) |
Ответы |
Re: cataloguing NOT NULL constraints
|
Список | pgsql-hackers |
On Tue, Jul 25, 2023 at 1:33 PM Isaac Morland <isaac.morland@gmail.com> wrote: > My suggestion is for \d+ to show NOT NULL constraints only if there is something weird going on (wrong name, duplicateconstraints, …). If there is nothing weird about the constraint then explicitly listing it provides absolutely noinformation that is not given by "not null" in the "Nullable" column. Easier said than done I suppose. I'm just worriedabout my \d+ displays becoming less useful. I mean, the problem is that if you want to ALTER TABLE .. DROP CONSTRAINT, you need to know what the valid arguments to that command are, and the names of these constraints will be just as valid as the names of any other constraints. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: