| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, Martijn van Oosterhout <kleptog(at)svana(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-20 04:29:24 |
| Message-ID: | 16675.1166588964@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> Force references to go through macros which implement the lookup for the
> appropriate type? ie: LOGICAL_COL(table_oid,2) vs.
> PHYSICAL_COL(table_oid,1) Perhaps that's too simplistic.
It doesn't really address the question of how you know which one to
use at any particular line of code; or even more to the point, what
mechanism will warn you if you use the wrong one.
My gut feeling about this is that we could probably enforce such a
distinction if we were using C++, but while coding in C I have no
confidence in it. (And no, that's not a vote to move to C++ ...)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shane Ambler | 2006-12-20 04:34:55 | Re: effective_cache_size vs units |
| Previous Message | Joshua D. Drake | 2006-12-20 04:23:22 | Re: Companies Contributing to Open Source |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-12-20 11:03:11 | Re: [HACKERS] Enums patch v2 |
| Previous Message | Stephen Frost | 2006-12-20 04:12:50 | Re: column ordering, was Re: [PATCHES] Enums patch v2 |