> -----Original Message-----
> From: pgadmin-hackers-owner@postgresql.org
> [mailto:pgadmin-hackers-owner@postgresql.org] On Behalf Of
> Ivan Nejgebauer
> Sent: 23 September 2004 09:33
> To: pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] Repost: Patch: view data for
> tables/views on
>
> Dave Page wrote:
> > I think this is exactly when it should be enabled - such
> that you have
> > the choice that double click can do one of the following:
> >
> > - Nothing
> > - Open the data view on a table/view (and nothing on other objects)
> > - Open the properties dialogue.
>
> I thought about that, too, but that would be (IMO) better
> achieved with radio buttons or a combination of a checkbox
> and radio buttons, and I didn't want to rearrange the dialog
> too drastically.
I think 3 radio buttons would work the best - sometimes you just have to
bite the bullet and redesign the dialogues :-)
> but a higher limit is there to prevent
> memory exhaustion and application trashing should you choose
> to view a hypothetical million-row table.
Of course - I think it's a good idea, it just needs to warn the user
when it limits the recordset. Let's use the same default as the existing
setting, and keep the limits separate - I think that might be useful as
you suggest.
> That's fine by me -- I see pgAdmin as a very nice and useful
> tool, which is why I want to contribute to its development in
> the first place, and I realize the need for thoroughly
> discussing any proposed addition.
:-) I think you just happened to pick one of those topics that was bound
to cause some discussion!
Regards, Dave
