Board index PostgreSQL

Demo patch for DROP COLUMN

Demo patch for DROP COLUMN

Post by Christopher Kings-Lynn » Thu, 25 Jul 2002 10:45:07



Quote:> > My point was that there could still be a conflict against a user column
> > that the user tries to create *later*.  So it's illusory to think that
> > making the name of a dropped column less predictable will improve
> > matters.

> The simple (to describe, perhaps not to implement ;) way to resolve it
> would be for the ADD COLUMN (or CREATE TABLE INHERITS) rename the
> offending deleted column once more.

Hah! What a wonderful idea!  Now why didn't I think of that!

Chris

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

 
 
 
Top

1. Demo patch for DROP COLUMN

My point was that there could still be a conflict against a user column
that the user tries to create *later*.  So it's illusory to think that
making the name of a dropped column less predictable will improve
matters.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate

message can get through to the mailing list cleanly

2. Remove Seconds?

3. Aggregation vs Calculation

4. 7.3 and HEAD broken for dropped columns of dropped types

5. CENTRAL US-CONSULTANT POSITIONS-RDBMS TECHNOLOGY-ORACLE PREFERRED

6. grep and awk Demo to Drop Foreign Keys

7. Getting "Columns in Order by list must be unique" on a UPDATE statment

8. Drop a column and add a new column

9. Problem with DROP COLUMN and ALTER COLUMN

10. Dropping column silently kills multi-coumn index (was [ODBC] Error when accessing tables with deleted columns)

11. How to change a column's type/How to drop a column

12. Dropping column silently kills multi-coumn index (was [ODBC] Error when accessing tables with deleted columns)


All times are UTC
Board index