Re: PgAccess directory structure - Mailing list pgsql-interfaces

From Tom Lane
Subject Re: PgAccess directory structure
Date
Msg-id 29968.1021218729@sss.pgh.pa.us
Whole thread Raw
In response to Re: PgAccess directory structure  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: PgAccess directory structure
List pgsql-interfaces
Peter Eisentraut <peter_e@gmx.net> writes:
> Keeping a separate file for each version may lead to a lot of duplicate
> code being necessary and hard to maintain.

Peter has a good point: you'll almost certainly end up with lots of
duplicate code to maintain if you try to split at the file level.
"If"s seem to work well enough in pg_dump.

Another potential objection to the scheme as you proposed it is that
any given instance of pgaccess could only talk to one backend version.
I dunno whether pgaccess supports multiple connections now or might
do so in the future --- but if that's of interest, adapting to backend
version on-the-fly is a lot better than loading different versions of
support code at startup.
        regards, tom lane


pgsql-interfaces by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: PgAccess directory structure
Next
From: "Nigel J. Andrews"
Date:
Subject: Re: PgAccess directory structure