Re: Using "object orientated" tables?

On Tue, May 10, 2022 at 6:33 PM Simon Connah <simon(dot)n(dot)connah(at)protonmail(dot)com>
wrote:

> Hi,
>
> I was wondering what the community thought of using table inheritance in
> PostgreSQL? Is it considered bad practice these days?
>
> Basically, I have a users table and every user has a unique, not null UUID
> which is used as the primary key. There are only three columns on the
> table. User ID, Username, Email.
>
> Having said that I'll have to store data about them which I don't want to
> do in one massive table as it would be ugly as hell. So what I want is my
> main user's table to stick to three columns and then sub-tables which
> inherit from it to add their own column? So for instance I might want to
> store an account balance for people making money on my site.
>
> Hopefully, I've managed to explain what I mean properly. If you need any
> extra information then let me.
>
>
I wouldn't use inheritance, especially since I do not want to carry around
copies of Username and Email. Having a "core data" users table then adding
additional one-to-one related tables based upon application needs is quite
common.

David J.