From: | Jan Johansson <jan(dot)johansson(dot)mr(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Inheritance |
Date: | 2016-05-22 06:37:01 |
Message-ID: | CAGbXvMY_Ca0XtuENdrCznTgYs-YzWbLEz5nQSzcNpP-H7BbCbg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I've been reading some threads about inheritance, and how complicated it
seems to let child (children) to inherit constraints and indexes
(behaviors). In fact this seems to have been the issue for years, with no
resolution.
However, inheritance is a very good feature, and it would be great to have
it feature complete.
To try to unlock the feature, to be more complete, how about introducing
restriction to inheritance like:
- Allow single (behavior) inheritance (model here is quite a few modern
languages, such as C#, D, ...)
- Allow multiple declarative inheritance (interface like, the inheritance
almost works like this today though)
If, with these restrictions (or maybe only the first), do you think that it
will simplify implementation and make it more feature complete?
Kind regards,
Jan Johansson
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2016-05-22 08:31:35 | Re: Parallel query |
Previous Message | Peter Geoghegan | 2016-05-22 00:03:41 | Re: BUG #14153: Unrecognized node type error when upsert is present in recursive CTE |