Re: Refactoring psql for backward-compatibility - Mailing list pgsql-hackers

From David Fetter
Subject Re: Refactoring psql for backward-compatibility
Date
Msg-id 20051215013537.GB6529@fetter.org
Whole thread Raw
In response to Re: Refactoring psql for backward-compatibility  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: Refactoring psql for backward-compatibility  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-hackers
On Thu, Dec 15, 2005 at 09:20:46AM +0800, Christopher Kings-Lynne wrote:
> >Neil Conway suggested something like a get_function_list(), which I
> >presume would be called on connect, and would be version-aware.
> >Does this seem like a good idea?  If so, what might an
> >implementation look like?  I know C isn't all that great for
> >function overloading, so do we want to keep all the SQL for all
> >previous versions in memory, or...?
> 
> If it was me I'd just copy the pg_dump way of doing things...

To the extent possible, I'd like to preserve the exact functionality
(or lack thereof) of previous versions.  Would this be possible that
way?

Cheers,
D
-- 
David Fetter david@fetter.org http://fetter.org/
phone: +1 415 235 3778

Remember to vote!


pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: Immodest Proposal: pg_catalog.pg_ddl
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Refactoring psql for backward-compatibility