Laurent ROCHE a écrit :
> Just to clarify what I mean.
> I am quite happy (or should I say: not too unhappy) to juggle with different
> version of pg_dump in my scripts.
> If that's the way it has to be, that's the way it has to be.
> See point A, below.
>
> But to me pgAdmin is a tool that must
Hi,
Just to clarify what I mean.
I am quite happy (or should I say: not too unhappy) to juggle with different
version of pg_dump in my scripts.
If that's the way it has to be, that's the way it has to be.
See point A, below.
But to me pgAdmin is a tool that must be easy to use.
Hence, as it seem
On 19/06/2007 14:36, Dave Page wrote:
Raymond O'Donnell wrote:
Agreed - an option in the preferences to specify the path to the desired
pg_dump would certainly be useful.
Already in the next release.
Great!
another one with all compatible tools versions to be able to work
correctly on d
Raymond O'Donnell wrote:
> On 19/06/2007 13:54, Laurent ROCHE wrote:
>
>> May be that's a pg_dump issue: it should be compatible with the
>> server it connects to, and not to its own version ?
>
> What do you mean?
Shipping every version of pg_dump, libpq & supporting DLL's back to v7.3
by the s
On 19/06/2007 13:54, Laurent ROCHE wrote:
May be that's a pg_dump issue: it should be compatible with the
server it connects to, and not to its own version ?
What do you mean?
Still meanwhile I would think pgAdmin should allow installing other
pg_dump executable.
I'm fairly sure that pgAdm
