Re: PgAccess directory structure

Поиск
Список
Период
Сортировка
Искать
От
Peter Eisentraut
Тема
Re: PgAccess directory structure
Дата
в 05:24:01
Msg-id
Pine.LNX.4.44.0205112350230.828-100000@localhost.localdomain
Ответ на
PgAccess directory structure (Nigel J. Andrews)
Список
Дерево обсуждения
PgAccess directory structure "Nigel J. Andrews" <nandrews@investsystems.co.uk>
Re: PgAccess directory structure "Ross J. Reedstrom" <reedstrm@rice.edu>
Re: PgAccess directory structure Peter Eisentraut <peter_e@gmx.net>
Re: PgAccess directory structure Tom Lane <tgl@sss.pgh.pa.us>
Re: PgAccess directory structure "Nigel J. Andrews" <nandrews@investsystems.co.uk>
Re: PgAccess directory structure "C. Maj" <cmaj@freedomcorpse.info>
Nigel J. Andrews writes:

> That the lib directory gain one level of subdirectories called
> Pg, 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@gmx.net


В списке pgsql-interfaces по дате отправления
От: Nigel J. Andrews
Дата:
Сообщение: Re: [HACKERS] internal voting
От: Tom Lane
Дата:
FAQ