Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This - Mailing list pgsql-general

From Achilleas Mantzios
Subject Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This
Date
Msg-id d7e78923-b43c-4f1b-b3d5-82032dc9749a@cloud.gatewaynet.com
Whole thread Raw
In response to Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-general
Στις 23/10/23 20:06, ο/η Laurenz Albe έγραψε:
> On Mon, 2023-10-23 at 19:49 +0300, Achilleas Mantzios wrote:
>> Tom Lane wrote:
>>>   But there are valid use-cases where you
>>> actually do want more columns in the child tables than the parent.
>> also data departmentalization, consolidation, multi-tenancy are fine use
>> cases (same # and types of columns), you can't have writable VIEWs with
>> UNION, for me inheritance is a fantastic feature that I use with success
>> for some very important projects.
> Yes, there are valid and interesting use cases, although you have to
> search for them.  I am sure it can make an interesting talk.

Thank you, I hope so.

In my job, family owned business,  shipping, different types of vessels, 
different business for each type of vessel  both conceptually / 
functionally and materially , multi-tenancy (ok the illusion of many 
different systems) + the need of top view of the organization, it fitted 
like a globe.

>
> Yours,
> Laurenz Albe

-- 
Achilleas Mantzios
  IT DEV - HEAD
  IT DEPT
  Dynacom Tankers Mgmt




pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Passing enum Parameters to User-defined C-Language Functions
Next
From: Achilleas Mantzios
Date:
Subject: Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This