What did you expect?
Jens Schicke wrote:
> pizza_de=# alter table store_flags add column flag integer;
> ALTER TABLE
> pizza_de=# alter table store_flags drop column flag;
> ALTER TABLE
> pizza_de=# alter table store_flags add column flag integer not null;
> ERROR: column "flag" contains null values
The column was not added. It would've been filled with NULLs, which
would violate the NOT NULL constraint. You have to give a DEFAULT if you
add a column with a NOT NULL constraint.
> pizza_de=# alter table store_flags drop column flag;
> ERROR: column "flag" of relation "store_flags" does not exist
The column doesn't exist, because the add column above failed, and was
rolled back.
> pizza_de=# alter table store_flags add column flag integer not null;
> ERROR: column "flag" contains null values
Same as above..
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com