Re: Query results in grid, new patch
От | Dave Page |
---|---|
Тема | Re: Query results in grid, new patch |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E4011C927C@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 22:56 > 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 > > > We have discussed this previously. Trying to extend the query > tool to a > multi purpose data manipulating tool is a dead end. We discussed it, but we certainly didn't agree on that point. Besides, I fail to see how speeding up the grid and allowing copy/paste to be more flexible can possibly cause you any problems with checking query results and timing? The original argument was about 2 things: 1) Editting in the grid. Well, that's not gonna happen as we have a specialised tool for that. 2) Using a cursor based query to allow querying of very large data sets. Yes, I can see how that would prevent you (and others) from using the query tool in certain use cases, so I would definitely not advocate such a change *unless* it could be an option that unless selected did not change the current behaviour. > Finally, don't > forget: My initial impulse to code on pga3 was dissatisfaction with > pga2's query tool, so I'm most sensitive on that topic. I haven't forgotten, but I would ask you not to forget that pgAdmin is a community project written for general use and we shall not avoid implementing features that the community might want just because any one of us might not use them. That does not mean we should break things for existing use cases though. Regards, Dave.
В списке pgadmin-hackers по дате отправления: