Re: Refactoring psql for backward-compatibility

Поиск
Список
Период
Сортировка
Искать
От
Christopher Kings-Lynne
Тема
Re: Refactoring psql for backward-compatibility
Дата
Msg-id
43A0CC58.4060001@familyhealth.com.au
Ответ на
Список
Дерево обсуждения
Refactoring psql for backward-compatibility David Fetter <david@fetter.org>
Re: Refactoring psql for backward-compatibility Hannu Krosing <hannu@skype.net>
Re: Refactoring psql for backward-compatibility Martijn van Oosterhout <kleptog@svana.org>
Re: Refactoring psql for backward-compatibility Andrew Dunstan <andrew@dunslane.net>
Re: Refactoring psql for backward-compatibility Alvaro Herrera <alvherre@commandprompt.com>
Re: Refactoring psql for backward-compatibility Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: Refactoring psql for backward-compatibility David Fetter <david@fetter.org>
Re: Refactoring psql for backward-compatibility Christopher Kings-Lynne <chriskl@familyhealth.com.au>
>>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?

Don't see it'd be too hard.  All pg_dump basically does is this:

if (version <= 7.3) {  query = "..";
else if (version == 7.4) {  query = "..";
else  query = "..";

Other than that you might need some smarts in the output table display 
logic so that it doesn't "assume" what columns are available from the 
queries.

Or something.

Chris


В списке pgsql-hackers по дате отправления
От: David Fetter
Дата:
От: Tom Lane
Дата:
FAQ