Tim Perdue <[EMAIL PROTECTED]> writes:
> I see there are a handful of reports of this, but it does seem broken to
> me. If I am copying a table and a column is blank, surely it makes sense
> to substitute the column default from the table?
There is no such concept as "blank" in SQL.
7.3 does have the ability to COPY a subset of a column's tables and
insert default values for the omitted columns. But if a column is
provided in the input, there is no clean way to decide that a particular
input value ought to be replaced by a default.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
