Tom Lane <tgl@xxxxxxxxxxxxx> writes:
> And it's been looked at a few times, and rejected as being far too
> bug-prone. The number of ways to screw up by using physical column
> number where you should have used logical, or vice versa, is daunting.
One way to make sure there are no such bugs would be to make sure the two sets
of values are completely incompatible. So any attempt to use the wrong one
would *always* cause a bug rather than just sometimes.
Say by making one set have an offset of 1000 or be negative and have the
functions/macros that handle this assert() the correct range before
adjusting and proceeding.
--
greg
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
