Oliver Elphick writes:
> Peter Eisentraut wrote:
> >Tom Lane writes:
> >
> >> It seems that in pre-7.0 Postgres, this works:
> >>
> >> create table one(id int default 1, descr text);
> >> create table two(id int default 2, tag text) inherits (one);
> >>
> >> with the net effect that table "two" has just one "id" column with
> >> default value 2.
> >
> >Although the liberty to do anything you want seems appealing at first, I
> >would think that allowing this is not correct from an OO point of view.
>
> I don't agree; this is equivalent to redefinition of a feature (=method) in
> a descendant class, which is perfectly acceptable so long as the feature's
> signature (equivalent to column type) remains unchanged.
The SQL equivalent of redefining a method would the redefinition of a
method [sic]. But since we don't have anything close to that, feel
free...
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
