pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This
Date: Mon, 23 Oct 2023 20:13:11 +0300
Message-ID: <d7e78923-b43c-4f1b-b3d5-82032dc9749a@cloud.gatewaynet.com> (raw)
In-Reply-To: <51f4369e3ebde2652709715da3052650e0f1042a.camel@cybertec.at>
References: <2f106761-daa8-6b26-013e-884da25322c2@cloud.gatewaynet.com>
	<374847.1698071743@sss.pgh.pa.us>
	<23469ec0-674e-470a-b6eb-dfcb376c5049@cloud.gatewaynet.com>
	<51f4369e3ebde2652709715da3052650e0f1042a.camel@cybertec.at>

Στις 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






view thread (14+ messages)  latest in thread

Message-ID: <d7e78923-b43c-4f1b-b3d5-82032dc9749a@cloud.gatewaynet.com>
Permalink:  ../d7e78923-b43c-4f1b-b3d5-82032dc9749a@cloud.gatewaynet.com/
Also on:    postgresql.org/message-id/d7e78923-b43c-4f1b-b3d5-82032dc9749a@cloud.gatewaynet.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: a.mantzios@cloud.gatewaynet.com, laurenz.albe@cybertec.at, tgl@sss.pgh.pa.us
  Subject: Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This
  In-Reply-To: <d7e78923-b43c-4f1b-b3d5-82032dc9749a@cloud.gatewaynet.com>
  References: <2f106761-daa8-6b26-013e-884da25322c2@cloud.gatewaynet.com> <374847.1698071743@sss.pgh.pa.us> <23469ec0-674e-470a-b6eb-dfcb376c5049@cloud.gatewaynet.com> <51f4369e3ebde2652709715da3052650e0f1042a.camel@cybertec.at> <d7e78923-b43c-4f1b-b3d5-82032dc9749a@cloud.gatewaynet.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox