Re: BUG #4056: problem creating function with domain argument

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #4056: problem creating function with domain argument
Дата
Msg-id 25114.1206640359@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BUG #4056: problem creating function with domain argument  ("Dave Page" <dpage@pgadmin.org>)
Ответы Re: BUG #4056: problem creating function with domain argument  ("Dave Page" <dpage@pgadmin.org>)
Список pgsql-bugs
"Dave Page" <dpage@pgadmin.org> writes:
> On Tue, Mar 25, 2008 at 5:37 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> ... It looks to me like pgAdmin is mistakenly
>> thinking that a domain has type modifiers.

> pgAdmin is using format_type() with a query like:

> postgres=# SELECT oid, format_type(oid, typtypmod) AS typname FROM
> pg_type where oid = 'dt_0'::regtype;
>   oid  | typname
> -------+----------
>  35130 | dt_0(36)
> (1 row)

> I would expect it to format the type appropriately.

No, the above is entirely wrong.  typtypmod is the typmod that goes with
the domain's base type, not with the domain itself.  You got away with
this mistaken code before 8.3 because format_type just silently ignored
its typmod argument for all but a very small number of types.  But now
the default behavior is to print the typmod.

When looking at a domain type, format_type(typbasetype,typtypmod)
would be a sane thing to do.  But that typmod isn't to be attached
to the domain itself.

            regards, tom lane

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

Предыдущее
От:
Дата:
Сообщение: Re: Extra empty lines PGv8.3.1
Следующее
От: "Eric P. Melbardis"
Дата:
Сообщение: Re: BUG #4056: problem creating function with domain argument