Re: column ordering, was Re: [PATCHES] Enums patch v2

Поиск
Список
Период
Сортировка
От Martijn van Oosterhout
Тема Re: column ordering, was Re: [PATCHES] Enums patch v2
Дата
Msg-id 20061221153703.GD14992@svana.org
обсуждение исходный текст
Ответ на Re: column ordering, was Re: [PATCHES] Enums patch v2  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: column ordering, was Re: [PATCHES] Enums patch v2  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: column ordering, was Re: [PATCHES] Enums patch v2  ("Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>)
Список pgsql-hackers
On Thu, Dec 21, 2006 at 10:27:12AM -0500, Andrew Dunstan wrote:
> >Um, surely you meant "offset the physical numbers". Imho the logical
> >numbers
> >need to stay 1-n, because those numbers are used way more often and are
> >more user visible than the physical.
> >
> >
> >
>
> I don't think we should expose the offset to user view at all - this is
> just for internal use, no?

The thing is, physical index numbers has meaning, the logical index
number does not. In a view definition we're going to store the physical
index, not the logical one, for example. We don't want rearranging
columns to invalidate view definitions or plans.

The number of places needing the logical index are not that man,
relativelyy, and given it has no intrinsic meaning, it's better to give
it a numeric value which is obviously abritrary (like 10001).

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: ERROR: tuple concurrently updated
Следующее
От: Tom Lane
Дата:
Сообщение: Re: New version of money type