Thanks Stephan. That appears to be the reason for the differences.
-Thusitha
Stephan Szabo <sszabo@megazone.bigpanda.com> wrote:
On Wed, 19 Apr 2006, Thusitha Kodikara wrote:
> Hi, > > I observed the following on PostgreSQL 8.1.3 (on Windows 2000). > > (1) alter table invoice add column active boolean default true; > > This will add a new column "active" with a default clause as "true" and > also sets the value "true" to all existing rows of the table. > > BUT > > (2) ALTER TABLE invoice ADD COLUMN active boolean; > ALTER TABLE invoice ALTER COLUMN active SET DEFAULT true; > > Will result in only adding the column "active" with default clause as > "true". It will NOT set the value "true" for existing rows. > > Is there a particular reason for this difference in behaviour? (Or am I > missing something in the syntax?)
AFAICS that's what the spec requires (at least in SQL92)
Add column says: 2) Let C be the column added to T. Every value in C is the default value for C.
So, in the first case, every value in the new column is true. In the second, at the point of the add column every value is null (since there's no default). Set default doesn't appear to change the value of existing rows, so no further change is made when you set default (ie, it doesn't matter if something was set to the default in the past, changing the default doesn't change the value as stored).
---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings