> -----Original Message----- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 04 November 2005 14:03 > To: Dave Page > Cc: pgadmin-hackers > Subject: Re: Query tool margin > > Dave Page wrote: > > > > > > > >>-----Original Message----- > >>From: Andreas Pflug [mailto:[EMAIL PROTECTED] > >>Sent: 04 November 2005 13:48 > >>To: Dave Page > >>Cc: pgadmin-hackers > >>Subject: Re: Query tool margin > >> > >>Use ConvertDialogToPixels. > >>I'm still not happy, do we really need this? 999 wouldn't be > >>enough, I > >>do have bigger scripts. Additionally, screenshots need to > be updated. > > > > > > I ran into the problem very recently when debugging some > functions - the > > backend helpfully told me where the problems were, but of > course, I had > > a script, not the function itself in the window that > reported the error. > > The marker should show you the failing line, observing an offset if > executed from a marked range; is that broken?
No, the function is not in the editor that reports the error, a script that calls it is. The best we can do with the marker in this case is mark the function call. The error from the backend tells me there is a problem on line X of the marked function, which I then investigate in a separate query window (with the create or replace function source). Which do you prefer - margin or status bar? Running low on time... :-) /D ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
