Re: Refactoring psql for backward-compatibility

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Refactoring psql for backward-compatibility
Date: 2005-12-14 14:06:49
Message-ID: 20051214140649.GB9278@surnet.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan wrote:
>
> David Fetter wrote:
>
> >I'd much appeciate tips, specific RTFMs and feedback on this so I can
> >get cracking on a patch.
>
> well, before you even start on a patch we should have agreement that
> this is a good idea, and an agreed design.
>
> This is really an m * n problem. That's what does indeed make it a
> maintenance nightmare. A new version of psql implements a new command
> and suddenly we have to provide compatibility versions (if possible) for
> m server versions back. Repeat for n versions of psql.

You just need to give the user a message saying "this server version
does not implement this command".

Of course, the design needs to support the fact that some server
versions will not implement all backslash commands. This should not be
too difficult.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-12-14 15:01:47 Re: Immodest Proposal: pg_catalog.pg_ddl
Previous Message Rod Taylor 2005-12-14 14:05:19 Re: Cost-based optimizers