| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, "Adam H(dot) Pendleton" <fmonkey(at)fmonkey(dot)net> |
| Cc: | "pgadmin-hackers" <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Smallint |
| Date: | 2003-08-18 18:33:30 |
| Message-ID: | 03AF4E498C591348A42FC93DEA9661B844B4AB@mail.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
> Sent: 18 August 2003 18:41
> To: Adam H. Pendleton
> Cc: pgadmin-hackers
> Subject: Re: [pgadmin-hackers] Smallint
>
>
> Adam H. Pendleton wrote:
>
> > Duh! Obviously it's not, it's just that pgAdmin3 calls it an int2?
> > Any reason not to call it a smallint, since that's they way it's
> > referred to in the documentation?
>
> Yeah.
> Virtually all types are read from the database. SMALLINT and
> INTEGER are
> parser translations, and there might be more. IMHO, the
> combobox already
> shows way to much.
>
> Only types that don't have a pg_type entry (serial,
> bigserial) are added
> manually.
For v2, perhaps we should default to an 'newbie mode' (obviously not
called that ;-) ) in which we list only the standard SQL types and their
array equivalents? I have seen datatype queries from newbies a number of
times in the past.
Regards, Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Howard Bagcat | 2003-08-18 21:13:41 | pgadmin3 on win98... |
| Previous Message | Andreas Pflug | 2003-08-18 17:40:43 | Re: Smallint |