Re: Query results in grid, new patch
От | Dave Page |
---|---|
Тема | Re: Query results in grid, new patch |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E4011C923F@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Query results in grid, new patch ("Edward Di Geronimo Jr." <edigeronimo@xtracards.com>) |
Список | pgadmin-hackers |
> -----Original Message----- > From: Andreas Pflug [mailto:pgadmin@pse-consulting.de] > Sent: 06 March 2006 13:12 > To: Dave Page > Cc: Florian G. Pflug; Edward Di Geronimo Jr.; > pgadmin-hackers@postgresql.org > Subject: Re: [pgadmin-hackers] Query results in grid, new patch > > Hu? I meant the control *does* remember column sizing for repeated > execution of similar queries since 1.2!!! This is not a "nice > fix", it > is *required*. Chill out - I meant that default sizing based on the width of the headers would be a nice fix so that the names weren't truncated. I will look at the size retention issue - I hadn't noticed that was broken. > I don't give a cent for copy/paste from the > result (in 10 > years on SQL RDBMS, I might have done that 5 times), I need > repeatable > results from query tuning. I on the other hand copy and paste data on a regular basis in SQL Enterprise Manager for example and will find this feature particularly useful in pgAdmin, as will other people I know both at work and in the community. As for repeatable query result timing, I see nothing in the patch that has made the timings non-repeatable, or even for that matter altered the initial query timing at all. > Trying to autosize the column from content doesn't work satisfying. No, and noone has suggested doing so. The headers on the other hand tend to have much more regular lengths. Regards, Dave
В списке pgadmin-hackers по дате отправления: