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

From: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
To: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net>, <pgsql-hackers(at)postgresql(dot)org>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Gregory Stark" <stark(at)enterprisedb(dot)com>
Subject: Re: column ordering, was Re: [PATCHES] Enums patch v2
Date: 2006-12-21 14:39:07
Message-ID: E1539E0ED7043848906A8FF995BDA57901A34E7A@m0143.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


> I'm not sure how much you can do with typing. Things like heap_getattr
> are macros, and thus untyped. Most places use attr as an index to an
> array, which also can't be type checked.
>
> If you switched everything over to inline functions you might
> get it to
> work, but that's about it.
>
> IMHO the best solution is to offset the logical numbers by some
> constant...

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.

Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2006-12-21 14:56:30 Re: Tuning single row operations
Previous Message Matthew O'Connor 2006-12-21 14:36:05 Re: Tuning single row operations

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2006-12-21 15:27:12 Re: column ordering, was Re: [PATCHES] Enums patch v2
Previous Message Zeugswetter Andreas ADI SD 2006-12-21 14:04:13 Re: Load distributed checkpoint