| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | "Obe, Regina" <robe(dot)dnd(at)cityofboston(dot)gov>, "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: Bug: PgAdmin not displaying typmod column types correctly in create or display |
| Date: | 2010-01-06 18:50:39 |
| Message-ID: | 937d27e11001061050u76225fe3q828ac1b5ce73f830@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Wed, Jan 6, 2010 at 6:45 PM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> The easy way to fix this is calling format_type in the query and giving
> it the atttypmod column of pg_attribute. I can't find if there are
> corner cases if I do this. Dave, do you know why there is a pgDatatype?
> it seems redundant with format_type. And the latter seems to work well
> whereas pgDatatype is surely wrong.
iirc, it was intended as a type formatting and caching mechanism, that
can not only format individual types, but can be used to populate
combo boxes and the like with sets of types/domains with minimal
overhead. For example, some of the dialogues can have quite a few
combos full of types on them, which are not always the same, and not
necessarily cheap to populate.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2010-01-06 23:50:16 | Re: Bug: PgAdmin not displaying typmod column types correctly in create or display |
| Previous Message | Guillaume Lelarge | 2010-01-06 18:45:24 | Re: Bug: PgAdmin not displaying typmod column types correctly in create or display |