Re: [pgadmin-hackers] Query results in grid, new patch
Andreas Pflug wrote: Dave Page wrote: On 6/3/06 19:04, "Andreas Pflug" <[EMAIL PROTECTED]> wrote: Dave Page wrote: NOT a todo. I found the result something between annoying and useless when I implemented column sizing preserving, esp. in case of many columns. I still didn't have the time to have a look at the patch, and I will be very unhappy if I find the result a regression because its functions are extended in a direction the control never was intended and designed for. If you find any breakages then do report them and I will look at them, but please do not forget that pgAdmin is not designed entirely for your usage patterns - just because you don't copy'n'paste query results doesn't mean there aren't a thousand people that do (or will do). We have discussed this previously. Trying to extend the query tool to a multi purpose data manipulating tool is a dead end. 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. Well, but that is what it is used for (as a "multi purpose data manipulation tool"). In the company I work for, nearly all kinds of postgres maintenance is done using pgadmin - from creating databases and schema manipulation, to debugging when some customers believes that some piece of data is wrong. So, I'd say, at least for us the query-window is the most important piece of pgadmin. And, most interesting, it's not big features that people miss in their daily work, it's the small useability things (like copying a over-long value of a textfield into an editor to be able to read it properly). greetings, Florian Pflug ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] Query results in grid, new patch
Dave Page wrote: On 6/3/06 19:04, "Andreas Pflug" <[EMAIL PROTECTED]> wrote: Dave Page wrote: NOT a todo. I found the result something between annoying and useless when I implemented column sizing preserving, esp. in case of many columns. I still didn't have the time to have a look at the patch, and I will be very unhappy if I find the result a regression because its functions are extended in a direction the control never was intended and designed for. If you find any breakages then do report them and I will look at them, but please do not forget that pgAdmin is not designed entirely for your usage patterns - just because you don't copy'n'paste query results doesn't mean there aren't a thousand people that do (or will do). We have discussed this previously. Trying to extend the query tool to a multi purpose data manipulating tool is a dead end. 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. Regards, Andreas ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] Query results in grid, new patch
On 6/3/06 19:04, "Andreas Pflug" <[EMAIL PROTECTED]> wrote: > Dave Page wrote: >> > > NOT a todo. I found the result something between annoying and useless > when I implemented column sizing preserving, esp. in case of many columns. > I still didn't have the time to have a look at the patch, and I will be > very unhappy if I find the result a regression because its functions are > extended in a direction the control never was intended and designed for. If you find any breakages then do report them and I will look at them, but please do not forget that pgAdmin is not designed entirely for your usage patterns - just because you don't copy'n'paste query results doesn't mean there aren't a thousand people that do (or will do). Regards, Dave. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [pgadmin-hackers] Query results in grid, new patch
Dave Page wrote: -Original Message- From: Florian G. Pflug [mailto:[EMAIL PROTECTED] Sent: 06 March 2006 03:37 To: Florian G. Pflug Cc: Dave Page; Edward Di Geronimo Jr.; pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Query results in grid, new patch I've finally come around to testing the new grid on osx, I must say that I'm really impressed. It seems much more responsive than the old one to me, and being able to copy rows, cols and fields to the clipboard really rockts. I have to rather small suggestions, though .) Ctrl-A (or Cmd-A on OSX) should select the whole table - it's a rather well established UI-standard I believe to let Ctrl-A/Cmd-A select the whole "whatever" you are currently editing. Fixed. .) Could the initial size of the columns be choosen so, that the captions are not cut off? Possible todo for anyone that wants to try it! NOT a todo. I found the result something between annoying and useless when I implemented column sizing preserving, esp. in case of many columns. I still didn't have the time to have a look at the patch, and I will be very unhappy if I find the result a regression because its functions are extended in a direction the control never was intended and designed for. Regards, Andreas ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-hackers] 1.4.2 uploaded
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Jyrki Wahlstedt > Sent: 06 March 2006 16:16 > To: pgadmin-hackers@postgresql.org > Subject: Re: [pgadmin-hackers] 1.4.2 uploaded > > Hi, > I have submitted the Portfile to DarwinPorts. The rest is on > other persons:-) Thanks :-) Regards, Dave ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [pgadmin-hackers] 1.4.2 uploaded
Hi, I have submitted the Portfile to DarwinPorts. The rest is on other persons:-) -- ! ! Jyrki Wahlstedt ! Männikkötie 5 D 19mob. +358-40-502 0164 skype:jyrkiwahlstedt ! FI-00630 Helsinki ! ! Our life is no dream; but it ought to become one and perhaps will. ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386 ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] 1.4.2 uploaded
> > P.S) > > I secured the 64-bit machine of Solaris. However, work is a schedule > > for next month by the reason no time is this month > > Raphaël may be quicker.:-) > > (He and I operated by solaris9. It had some frustration.. > > solaris10 is surely great.) > > But, there is no positive security. It is only my pleasure.:-) > > It might be better now - wxWidgets 2.6.3 (when it's out) contains some > important fixes for Solaris. In the meantime, CVS is your friend :-) > > http://people.planetpostgresql.org/dpage/index.php?/archives/39-Hello-Solaris,-Im-pgAdmin-III.ht ml Oooops.. pleasure doubled it.:-) Thank you for information..! Regards, Hiroshi Saito ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] 1.4.2 uploaded
> -Original Message- > From: Hiroshi Saito [mailto:[EMAIL PROTECTED] > Sent: 06 March 2006 15:45 > To: Dave Page > Cc: pgadmin-hackers > Subject: Re: [pgadmin-hackers] 1.4.2 uploaded > > Hi. > > FreeBSD was uploaded now.:-) Thanks. > P.S) > I secured the 64-bit machine of Solaris. However, work is a schedule > for next month by the reason no time is this month > Raphaël may be quicker.:-) > (He and I operated by solaris9. It had some frustration.. > solaris10 is surely great.) > But, there is no positive security. It is only my pleasure.:-) It might be better now - wxWidgets 2.6.3 (when it's out) contains some important fixes for Solaris. In the meantime, CVS is your friend :-) http://people.planetpostgresql.org/dpage/index.php?/archives/39-Hello-Solaris,-Im-pgAdmin-III.html /D ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] 1.4.2 uploaded
Hi. FreeBSD was uploaded now.:-) P.S) I secured the 64-bit machine of Solaris. However, work is a schedule for next month by the reason no time is this month Raphaël may be quicker.:-) (He and I operated by solaris9. It had some frustration.. solaris10 is surely great.) But, there is no positive security. It is only my pleasure.:-) Regards, Hiroshi Saito > Hi, > > I've uploaded 1.4.2 in source, win32, slackware-current and OSX Tiger > formats to http://developer.pgadmin.org/ftp/release/v1.4.2/ > > Hackers; please take a look and make sure there are no obvious problems > with any of them. > > Packagers; please upload your builds as soon as possible. > > If there are no showstoppers reported, I will announce the release > tomorrow. > > Cheers, Dave. ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-hackers] Query results in grid, new patch
> -Original Message- > From: Florian G. Pflug [mailto:[EMAIL PROTECTED] > Sent: 06 March 2006 03:37 > To: Florian G. Pflug > Cc: Dave Page; Edward Di Geronimo Jr.; pgadmin-hackers@postgresql.org > Subject: Re: [pgadmin-hackers] Query results in grid, new patch > > > I've finally come around to testing the new grid on osx, I must > say that I'm really impressed. It seems much more responsive than > the old one to me, and being able to copy rows, cols and fields > to the clipboard really rockts. I have to rather small > suggestions, though > > .) Ctrl-A (or Cmd-A on OSX) should select the whole table - it's > a rather well established UI-standard I believe to let Ctrl-A/Cmd-A > select the whole "whatever" you are currently editing. Fixed. > .) Could the initial size of the columns be choosen so, that > the captions > are not cut off? Possible todo for anyone that wants to try it! > Or, even better, pgadmin could remember the > with of the columns > between selects, at least if the captions stay the same... Fixed. > .) On OSX, the gray background looks rather strange, white > would be a better choice I believe. That seems to be the default for the grid control on OSX (see the Edit Grid which is also gray). It is white on other platforms though - I'll see if I can find a safe way to change it which won't affect people with 'negative' color schemes. Cheers, Dave. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[pgadmin-hackers] 1.4.2 uploaded
Hi, I've uploaded 1.4.2 in source, win32, slackware-current and OSX Tiger formats to http://developer.pgadmin.org/ftp/release/v1.4.2/ Hackers; please take a look and make sure there are no obvious problems with any of them. Packagers; please upload your builds as soon as possible. If there are no showstoppers reported, I will announce the release tomorrow. Cheers, Dave. ---(end of broadcast)--- TIP 6: explain analyze is your friend
[pgadmin-hackers] SVN Commit by dpage: r5046 - trunk/pgadmin3/src/ctl
Author: dpage Date: 2006-03-06 14:13:43 + (Mon, 06 Mar 2006) New Revision: 5046 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=5046&view=rev Log: Fix column size retention Modified: trunk/pgadmin3/src/ctl/ctlSQLResult.cpp ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[pgadmin-hackers] SVN Commit by dpage: r5045 - trunk/pgadmin3/src/frm
Author: dpage Date: 2006-03-06 14:03:09 + (Mon, 06 Mar 2006) New Revision: 5045 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=5045&view=rev Log: Fix Select-All in the query tool results pane. Modified: trunk/pgadmin3/src/frm/frmQuery.cpp ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-hackers] Query results in grid, new patch
Andreas Pflug wrote: > Dave Page wrote: >>> -Original Message- >>> From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 06 March >>> 2006 09:42 >>> To: Florian G. Pflug >>> Cc: Dave Page; Edward Di Geronimo Jr.; pgadmin-hackers@postgresql.org >>> Subject: Re: [pgadmin-hackers] Query results in grid, new patch >>> >>> Florian G. Pflug wrote: >>> >>> .) Could the initial size of the columns be choosen so, >>> that the captions are not cut off? Or, even better, >>> pgadmin could remember the with of the >>> columns between selects, at least if the captions stay the same... >>> >>> The old control's behaviour was like that. >> >> Yes, it was, but it might be a nice fix. It's bugged me for a while. > > 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*. 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. > Trying to autosize the column from content doesn't work satisfying. I've seem to have never noticed that.. ;-) I guess it's because most times i switch between two or more different queries, and the code doesn't handle that. I just experimented a bith with the latest 1.4 snapshot, and found a bug - it seems like a columns with is only remembered when the column "moves to the right", not when it "moves to the left". Another usefull feature (If it isn't already there, just under my nose ;-) ) would be to have tooltips displaying the full name of a column. I often resize the columns to be just wide enough to show the data, and more often than not, the caption is far longer than that. greetings, Florian Pflug ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-hackers] Query results in grid, new patch
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > 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 ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] Query results in grid, new patch
Dave Page wrote: -Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 06 March 2006 09:42 To: Florian G. Pflug Cc: Dave Page; Edward Di Geronimo Jr.; pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Query results in grid, new patch Florian G. Pflug wrote: .) Could the initial size of the columns be choosen so, that the captions are not cut off? Or, even better, pgadmin could remember the with of the columns between selects, at least if the captions stay the same... The old control's behaviour was like that. Yes, it was, but it might be a nice fix. It's bugged me for a while. 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*. 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. Trying to autosize the column from content doesn't work satisfying. Regards, Andreas ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[pgadmin-hackers] SVN Commit by dpage: r5044 - tags/REL-1_4_2
Author: dpage Date: 2006-03-06 12:32:12 + (Mon, 06 Mar 2006) New Revision: 5044 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=5044&view=rev Log: Tag 1.4.2 release Added: tags/REL-1_4_2/pgadmin3/ ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[pgadmin-hackers] SVN Commit by dpage: r5043 - tags
Author: dpage Date: 2006-03-06 12:31:45 + (Mon, 06 Mar 2006) New Revision: 5043 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=5043&view=rev Log: Create REL-1_4_2 tag. Added: tags/REL-1_4_2/ ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[pgadmin-hackers] SVN Commit by dpage: r5042 - branches/REL-1_4_0_PATCHES/pgadmin3/src/include/base
Author: dpage Date: 2006-03-06 12:00:08 + (Mon, 06 Mar 2006) New Revision: 5042 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=5042&view=rev Log: Fix multiline comment Modified: branches/REL-1_4_0_PATCHES/pgadmin3/src/include/base/base.h ---(end of broadcast)--- TIP 6: explain analyze is your friend
[pgadmin-hackers] SVN Commit by dpage: r5041 - in branches/REL-1_4_0_PATCHES/pgadmin3: . pkg/fc1 pkg/mandrake pkg/redhat pkg/src pkg/suse src/include
Author: dpage Date: 2006-03-06 11:36:26 + (Mon, 06 Mar 2006) New Revision: 5041 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=5041&view=rev Log: Prep for 1.4.2 Modified: branches/REL-1_4_0_PATCHES/pgadmin3/configure.ac branches/REL-1_4_0_PATCHES/pgadmin3/pkg/fc1/pgadmin3.spec branches/REL-1_4_0_PATCHES/pgadmin3/pkg/mandrake/pgadmin3.spec branches/REL-1_4_0_PATCHES/pgadmin3/pkg/redhat/pgadmin3.spec branches/REL-1_4_0_PATCHES/pgadmin3/pkg/src/build-tarball branches/REL-1_4_0_PATCHES/pgadmin3/pkg/suse/pgadmin3.spec branches/REL-1_4_0_PATCHES/pgadmin3/src/include/version.h ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[pgadmin-hackers] SVN Commit by dpage: r5040 - trunk/pgadmin3
Author: dpage Date: 2006-03-06 11:20:58 + (Mon, 06 Mar 2006) New Revision: 5040 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=5040&view=rev Log: Changelog update. Modified: trunk/pgadmin3/CHANGELOG ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] [patch] Please drop the dangerous libssl and libcrypto deps
Thanks, (updated) patch applied to SVN trunk. Regards. Dave > -Original Message- > From: Raphaël Enrici [mailto:[EMAIL PROTECTED] > Sent: 26 December 2005 22:58 > To: Dave Page; Adam H.Pendleton; Andreas Pflug; PgAdmin Hackers > Cc: Loïc Minier > Subject: [patch] Please drop the dangerous libssl and libcrypto deps > > Dear friends, > > Loic Minier(CCed) provided a patch to prevent pgadmin3 1.2.2 > from being > linked to a different libssl version than libpq when dynamically built > with an already ssl enabled libpq. The full bug report and original > patch by Loic can be found at > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341117 > > Attached is an svn diff for 1.4.1 release that I'm using for > the package > I'm about to upload to Debian (patch_libpqssl_1.4.1). > You'll also find a fully untested patch for trunk > (patch_libpqssl_current). > > Please recheck and apply if eveything's ok with them. > > Cheers, > Raph > ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[pgadmin-hackers] SVN Commit by dpage: r5039 - trunk/pgadmin3
Author: dpage Date: 2006-03-06 11:13:24 + (Mon, 06 Mar 2006) New Revision: 5039 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=5039&view=rev Log: Don't double-link libssl/libcrypto [Lo?\195?\175c Minier] Modified: trunk/pgadmin3/acinclude.m4 ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgadmin-hackers] Query results in grid, new patch
> -Original Message- > From: Edward Di Geronimo Jr. [mailto:[EMAIL PROTECTED] > Sent: 28 February 2006 19:00 > To: Dave Page > Cc: pgadmin-hackers@postgresql.org > Subject: RE: [pgadmin-hackers] Query results in grid, new patch > > > OK, can this be solved with wx ctlGrid class derived from > wxGrid that > > does a SetFocus on itself when a column or row is selected? > > I registered a handle for the selection event, and put in a call to > SetFocus. Seems to work now. > > > Thanks, looking good. We should probably tweak the edit > grid to match > > the left justified style when this gets accepted. > > Added that change in. Thanks, patch applied. Regards, Dave. ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [pgadmin-hackers] Query results in grid, new patch
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 06 March 2006 09:42 > To: Florian G. Pflug > Cc: Dave Page; Edward Di Geronimo Jr.; pgadmin-hackers@postgresql.org > Subject: Re: [pgadmin-hackers] Query results in grid, new patch > > Florian G. Pflug wrote: > > > > > .) Could the initial size of the columns be choosen so, > that the captions > > are not cut off? Or, even better, pgadmin could remember > the with of the > > columns > > between selects, at least if the captions stay the same... > > The old control's behaviour was like that. Yes, it was, but it might be a nice fix. It's bugged me for a while. /D ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Query results in grid, new patch
Florian G. Pflug wrote: .) Could the initial size of the columns be choosen so, that the captions are not cut off? Or, even better, pgadmin could remember the with of the columns between selects, at least if the captions stay the same... The old control's behaviour was like that. Regards, Andreas ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[pgadmin-hackers] SVN Commit by dpage: r5038 - in trunk/pgadmin3: . src/ctl src/frm src/include/ctl
Author: dpage Date: 2006-03-06 09:01:49 + (Mon, 06 Mar 2006) New Revision: 5038 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=5038&view=rev Log: Replace the query tool's wxListView control with a wxGrid and a virtual table to hold the data during loading for significant speedup. Enhance the query tool to allow copy/paste of arbitrary groups of columns, rows or individual cells. [Edward Di Geronimo Jr] Modified: trunk/pgadmin3/CHANGELOG trunk/pgadmin3/src/ctl/ctlSQLResult.cpp trunk/pgadmin3/src/frm/frmEditGrid.cpp trunk/pgadmin3/src/frm/frmExport.cpp trunk/pgadmin3/src/frm/frmQuery.cpp trunk/pgadmin3/src/include/ctl/ctlSQLResult.h ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] 1.4.2?
> -Original Message- > From: Raphaël Enrici [mailto:[EMAIL PROTECTED] > Sent: 06 March 2006 08:19 > To: Dave Page > Cc: Andreas Pflug; pgadmin-hackers > Subject: Re: [pgadmin-hackers] 1.4.2? > > mmmh take a look at the patch... Should be ok. I have, and yes, it /should/, but I've seen enough weird link failures caused by missing libs that were thought not to be needed for it to make me nervous. You can obviously test it properly on Debian though, so it you want a port specific patch I don't object. I'll certainly apply the patch in trunk though (perhaps modified a little as I've been rehashing much of that code recently). Regards, Dave ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] 1.4.2?
Dave Page wrote: -Original Message- From: Raphaël Enrici [mailto:[EMAIL PROTECTED] Sent: 06 March 2006 08:08 To: Dave Page Cc: Andreas Pflug; pgadmin-hackers Subject: Re: [pgadmin-hackers] 1.4.2? Mainly because it got overlooked (sorry). It won't go onto the stable branch anyway though - we never had a bug report about it (just the patch), At least we got one bug report... see bug #341117 at debian.org [1] :) s/we/debian :-) Debian -> community & I -> we ;) and I'm not prepared to modify that code with virtually zero field testing to 'fix' it in 1.4.x. I tested it myself ;) Just joking, I fully understand your position. However, can you please consider adding it for next release? I'll keep trace of it separately in debian packages until it's included upstream. Certainly. Of course, you are welcome to apply a platform specific mod to 1.4.2 for Debian only as it'll obviously work there. I'm more worried aboout breaking Solaris/FreeBSD etc. mmmh take a look at the patch... Should be ok. Maybe other maintainers could try it and report? Regards, Raph ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-hackers] 1.4.2?
> -Original Message- > From: Raphaël Enrici [mailto:[EMAIL PROTECTED] > Sent: 06 March 2006 08:08 > To: Dave Page > Cc: Andreas Pflug; pgadmin-hackers > Subject: Re: [pgadmin-hackers] 1.4.2? > > > Mainly because it got overlooked (sorry). It won't go onto > the stable branch anyway though - we never had a bug report > about it (just the patch), > > At least we got one bug report... see bug #341117 at debian.org [1] :) s/we/debian :-) > > and I'm not prepared to modify that code with virtually > zero field testing to 'fix' it in 1.4.x. > > I tested it myself ;) Just joking, I fully understand your position. > However, can you please consider adding it for next release? > I'll keep > trace of it separately in debian packages until it's included > upstream. Certainly. Of course, you are welcome to apply a platform specific mod to 1.4.2 for Debian only as it'll obviously work there. I'm more worried aboout breaking Solaris/FreeBSD etc. Regards, Dave ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgadmin-hackers] 1.4.2?
Dave Page wrote: -Original Message- From: Raphaël Enrici [mailto:[EMAIL PROTECTED] Sent: 04 March 2006 22:27 To: Andreas Pflug Cc: Dave Page; pgadmin-hackers Subject: Re: [pgadmin-hackers] 1.4.2? any reason why the patch concerning "double linkage"[1] issue has not been applied? Regards, Raphaël [1] http://archives.postgresql.org/pgadmin-hackers/2005-12/msg00170.php Hi Raph, Hi Dave, Mainly because it got overlooked (sorry). It won't go onto the stable branch anyway though - we never had a bug report about it (just the patch), At least we got one bug report... see bug #341117 at debian.org [1] :) and I'm not prepared to modify that code with virtually zero field testing to 'fix' it in 1.4.x. I tested it myself ;) Just joking, I fully understand your position. However, can you please consider adding it for next release? I'll keep trace of it separately in debian packages until it's included upstream. Cheers, Raph [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341117 ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
