So there are no simple way to do it right, and it will be not fixed? Will
this bug appear in todo list?
On Fri, Feb 26, 2010 at 6:13 PM, Greg Stark <gsstark@mit.edu> wrote:
> 2010/2/26 Oleg Serov <serovov@gmail.com>:
> > Up! Anybody will answer about the patch?
>
> The patch causes the inheritance history to be lost. If you
> subsequently drop the column form the parent it'll be kept on the
> child because it was explicitly declared when you created the child.
> In the original structure if you dropped the column from the parent it
> would be dropped from the child because it was an inherited column.
>
> Inheritance is in a kind of no-mans land. It's not good enough to be
> an important feature anyone cares enough about to make it work
> properly and it's not shoddy enough that it's worth removing. I'm sure
> there are people using it effectively despite the caveats and rough
> edges.
>
> --
> greg
>
--=20
=F3 =D5=D7=C1=D6=C5=CE=C9=C5=CD
=EF=CC=C5=C7 =F3=C5=D2=CF=D7
