Skip site navigation (1) Skip section navigation (2)

Re: PgAccess directory structure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>,pgsql-interfaces(at)postgresql(dot)org
Subject: Re: PgAccess directory structure
Date: 2002-05-12 15:52:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
Peter Eisentraut <peter_e(at)gmx(dot)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

In response to


pgsql-interfaces by date

Next:From: Nigel J. AndrewsDate: 2002-05-12 20:06:21
Subject: Re: PgAccess directory structure
Previous:From: Bartus LeventeDate: 2002-05-12 10:15:37
Subject: Re: [HACKERS] internal voting

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group