Christopher Kings-Lynne wrote:
With ever more larger businesses adopting PostgreSQL, and that leading
on to more places having several versions of PostgreSQL in operation
simultaneously (i.e. development vs production) we're probably going to
need to give psql the ability to handle whichever version of the PG
backend it happens to connect to.
Marc's suggestion of breaking psql into it's own sub-project makes good
sense from that point of view.
Hey, good point. Giving psql the ability to handle multiple backend
versions could be done in a number of ways.
Subproject or not, why don't we just rearrange psql to dynamically load a
library of functions, eg:
libpsql72.so
libpsql73.so
etc...
And in them you have functions like:
printTableDef();
printViewDef();
etc...
Is this very different from how it's done at present?
:-)
Regards and best wishes,
Justin Clift
Chris
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
