| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Jan Johansson <jan(dot)johansson(dot)mr(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Inheritance |
| Date: | 2016-05-23 15:21:59 |
| Message-ID: | 31767859-3f44-8cd7-cc27-84e4999f396d@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/22/16 1:37 AM, Jan Johansson wrote:
> - 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?
I think you'll need to be a bit more specific to elicit a response. What
exactly are you proposing to change?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-05-23 15:50:02 | Re: PATCH: Batch/pipelining support for libpq |
| Previous Message | Andreas Seltenreich | 2016-05-23 11:18:34 | Re: [sqlsmith] Failed assertions on parallel worker shutdown |