Re: per-column generic option

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: per-column generic option
Дата
Msg-id 1310478960-sup-8358@alvh.no-ip.org
обсуждение исходный текст
Ответ на Re: per-column generic option  (Shigeru Hanada <shigeru.hanada@gmail.com>)
Ответы Re: per-column generic option
Re: per-column generic option
Список pgsql-hackers
Excerpts from Shigeru Hanada's message of mar jul 12 03:11:54 -0400 2011:
> (2011/07/12 0:44), Peter Eisentraut wrote:
> > On lör, 2011-07-09 at 23:49 -0400, Alvaro Herrera wrote:
> >> The new ALTER TABLE grammar seems a bit strange -- ADD, SET, DROP.  Is
> >> this defined by the SQL/MED standard?  It seems at odds with our
> >> handling of attoptions
> >
> > Well, I believe the SQL/MED options were actually implemented first and
> > the attoptions afterwards.  But it's probably not unwise to keep them
> > separate, even though the syntaxes could have been made more similar.
> 
> As you say, syntax for attoptions/reloptions seem to satisfy the 
> requirement of SQL/MED; SET for ADD/SET and RESET for DROP.

Speaking of which -- what's the difference between ADD and SET for SQL/MED
options?

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID