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

Re: PgAccess directory structure

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: PgAccess directory structure
Date: 2002-05-12 09:23:29
Message-ID: Pine.LNX.4.44.0205112350230.828-100000@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-interfaces
Nigel J. Andrews writes:

> That the lib directory gain one level of subdirectories called
> Pg<postgres-version>, that code specific to backend version be placed in these
> directories and that version independent code by kept in the lib directory.

Other tools that try to handle more than one version usually just do a

if (backend_version < 7.2)
  do this;
else
  do that;

(examples: JDBC, ODBC, pg_dump).  (Even if "do this" would be empty, you
can print a message or something.)

Keeping a separate file for each version may lead to a lot of duplicate
code being necessary and hard to maintain.  (All the module-loading stuff
you mentioned makes my head spin, but I can understand an "if" statement
like the above. ;-) )

-- 
Peter Eisentraut   peter_e(at)gmx(dot)net


In response to

Responses

pgsql-interfaces by date

Next:From: Robert StaudingerDate: 2002-05-12 10:10:26
Subject: Re: Composite datatypes, dynamic member fields
Previous:From: Nigel J. AndrewsDate: 2002-05-11 21:57:45
Subject: Re: [HACKERS] internal voting

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