Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch
| От | Alvaro Herrera |
|---|---|
| Тема | Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch |
| Дата | |
| Msg-id | 1308954898-sup-3215@alvh.no-ip.org обсуждение исходный текст |
| Ответ на | Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch (Alvaro Herrera <alvherre@commandprompt.com>) |
| Ответы |
Re: Re: starting to review the Extend NOT NULL
representation to pg_constraint patch
|
| Список | pgsql-hackers |
So remind me ... did we discuss PRIMARY KEY constraints? Are they supposed to show up as inherited not null rows in the child? Obviously, they do not show up as PKs in the child, but they *are* not null so my guess is that they need to be inherited as not null as well. (Right now, unpatched head of course emits the column as attnotnull). In this case, the inherited name (assuming that the child declaration does not explicitely state a constraint name) should be the same as the PK, correct? It is unclear to me that primary keys shouldn't be inherited by default. But I guess that's a separate discussion. -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-hackers по дате отправления: