Re: SVN Commit by dpage: r5179 - in trunk/pgadmin3: . src/frm - Mailing list pgadmin-hackers

From Dave Page
Subject Re: SVN Commit by dpage: r5179 - in trunk/pgadmin3: . src/frm
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E40138845F@ratbert.vale-housing.co.uk
Whole thread Raw
In response to SVN Commit by dpage: r5179 - in trunk/pgadmin3: . src/frm  (svn@pgadmin.org)
Responses Re: SVN Commit by dpage: r5179 - in trunk/pgadmin3:  (Andreas Pflug <pgadmin@pse-consulting.de>)
List pgadmin-hackers

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
> Sent: 23 May 2006 15:45
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] SVN Commit by dpage: r5179 -
> in trunk/pgadmin3: . src/frm
>
> Another reason for me to fork, I'd never accept wasting space
> for this.

Wasting space that's not used anyway?

> I wonder when more useless info like current date/time, mem
> usage etc.

Why on earth would we add that? Current character is useful for
precisely the reason you note below.

> are added to the statusbar.
> If this was supposed to aid the ".. at character nnn" error
> messages (it doesn't unless the query starts at (0,0)),

No, in that case it doesn't help but that doesn't mean it isn't useful
in other situations.

> I
> already have an 8.2 compatible and enhanced error handling
> done, based on 5109 and thus uncommittable.

The current code works perfectly against CVS-tip from Friday. I was also
planning on adding a highlight to the word at the error position (taking
into account the actual start of the query). You are welcome to commit
what code you have though - I'm sure you're more than capable of merging
it.

Regards, Dave.

pgadmin-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: SVN Commit by dpage: r5179 - in trunk/pgadmin3:
Next
From: Andreas Pflug
Date:
Subject: Re: SVN Commit by dpage: r5179 - in trunk/pgadmin3: