| From: | Simon Connah <simon(dot)n(dot)connah(at)protonmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-novice(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Using "object orientated" tables? |
| Date: | 2022-05-11 01:52:59 |
| Message-ID: | GplscGquyyDz8je2GgcpHDCPH3ukKsBVcesYOPKad8WHDghgfl9IfM4aMYKcWA-BK6-PXcK1EqfGZI6k2-io8Vr3oaLlmmpJ4XyVYFBXxzw=@protonmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
------- Original Message -------
On Wednesday, May 11th, 2022 at 02:50, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>
> Simon Connah simon(dot)n(dot)connah(at)protonmail(dot)com writes:
>
> > I was wondering what the community thought of using table inheritance in PostgreSQL? Is it considered bad practice these days?
>
>
> Mmm ... not if the various caveats[1] don't bother you. The biggest
> stumbling block for most people, I think, is that you can't have
> foreign keys that reference the whole inheritance hierarchy.
>
> regards, tom lane
>
> [1] https://www.postgresql.org/docs/current/ddl-inherit.html#DDL-INHERIT-CAVEATS
Thank you. I'll be sure to read that.
Simon.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Froehlich | 2022-05-11 16:03:38 | RE: Using "object orientated" tables? |
| Previous Message | Simon Connah | 2022-05-11 01:51:49 | Re: Using "object orientated" tables? |