From: | "Dave Page" <dpage(at)pgadmin(dot)org> |
---|---|
To: | "Guillaume Lelarge" <guillaume(at)lelarge(dot)info> |
Cc: | "Magnus Hagander" <magnus(at)hagander(dot)net>, "Peter Gagarinov" <heartofmars(at)gmail(dot)com>, pgadmin-support(at)postgresql(dot)org |
Subject: | Re: bug in pgadmin 1.8.2: missing entry in 'Data Type' list |
Date: | 2008-02-13 14:58:58 |
Message-ID: | 937d27e10802130658w41763bcdud128f3636ab0cce1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Feb 13, 2008 2:56 PM, Guillaume Lelarge <guillaume(at)lelarge(dot)info> wrote:
> That's something I already heard at Solutions Linux 2008. I talked with
> someone who has this kind of issues. This guy has lots of tables, so his
> type combo box is really huge, and becomes actually unusable.
>
> Table types are perfectly valid and we need to have them, but the combo
> box becomes (is already?) unusable. We probably should think about
> designing if differently : for example a text box and a button. The text
> box allows someone to quickly, but manually, put a type, and the button
> allows to open a new window with a listbox containing all types and two
> checkboxes, one to add/remove array types, another one to add/remove
> table types.
OK, so I'm thinking for now then we should just remove table types
altogether - as Peter reports, we only show the array types anyway, so
I guess few people actually want to use them given that we've had no
prior complaints.
We can add a TODO to redesign things later.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2008-02-13 15:05:45 | Re: bug in pgadmin 1.8.2: missing entry in 'Data Type' list |
Previous Message | Guillaume Lelarge | 2008-02-13 14:56:35 | Re: bug in pgadmin 1.8.2: missing entry in 'Data Type' list |