Re: pgAdmin III: adjust code as per new EDB AS90 functions/procedures semantics - Mailing list pgadmin-hackers

From Magnus Hagander
Subject Re: pgAdmin III: adjust code as per new EDB AS90 functions/procedures semantics
Date
Msg-id AANLkTi=7sace0pCKTzsXWkfLdiD_VsOa48fN5aDm9mH2@mail.gmail.com
Whole thread Raw
In response to Re: pgAdmin III: adjust code as per new EDB AS90 functions/procedures semantics  (Dave Page <dpage@pgadmin.org>)
Responses Re: pgAdmin III: adjust code as per new EDB AS90 functions/procedures semantics
List pgadmin-hackers


On Feb 21, 2011 3:29 PM, "Dave Page" <dpage@pgadmin.org> wrote:
>
> Thanks Nikhil.
>
> Are there any catalog changes with the refactoring, that change the
> way parameters are represented that need to be reflected elsewhere in
> pgFunction.cpp?
>
> Also, does anyone object to back-patching this? It's not a bug fix,
> but it does mean that we don't support corresponding versions of PPAS
> and PG in the same version of pgAdmin which seems undesirable.

I wasn't aware they were supposed to be? Is that new, or has it always been?

More to the point - is this the only thing needed to reach compatibility? If so, i guess we can make an exception. If not, then there is no point without doing a bunch of more patches for other things, in which case i will object...

The
> patch is pretty straightforward and seems low risk.

This is of course a prerequisite in either case? I also assume it affects only an edbas codepath?

/Magnus

pgadmin-hackers by date:

Previous
From: Nikhil S
Date:
Subject: Re: pgAdmin III: adjust code as per new EDB AS90 functions/procedures semantics
Next
From: Dave Page
Date:
Subject: Re: pgAdmin III: adjust code as per new EDB AS90 functions/procedures semantics