Re: BETWEEN Node & DROP COLUMN - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: BETWEEN Node & DROP COLUMN
Date
Msg-id GNELIHDDFBOCMGBFGEFOEEPDCCAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: BETWEEN Node & DROP COLUMN  (Hiroshi Inoue <Inoue@tpf.co.jp>)
Responses Re: BETWEEN Node & DROP COLUMN
Re: BETWEEN Node & DROP COLUMN
List pgsql-hackers
> Unfortunately many apps rely on the fact that the attnos are
> consecutive starting from 1. It was the main reason why Tom
> rejected my trial. Nothing has changed about it.

OK, I've been looking at Hiroshi's implementation.  It's basically
semantically equivalent to mine from what I can see so far.  The only
difference really is in how the dropped columns are marked.

I've been ruminating on Hiroshi's statement at the top there.  What was the
reasoning for assuming that 'many apps rely on the fact that the attnos are
consecutive'?  Is that true?  phpPgAdmin doesn't.  In fact, phpPgAdmin won't
require any changes with Hiroshi's implementaiton and will require changes
with mine.

Anyway, an app that relies on consecutive attnos is going to have pain
skipping over attisdropped columns anyway???

In fact, I'm now beginning to think that I should just resurrect Hiroshi's
implementation.  I'm prepared to do that if people like...

Chris





pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: libpq++ build problems
Next
From: Tom Lane
Date:
Subject: Re: Adding attisdropped