RE: Using "object orientated" tables?

Just to pile on, this sounds like a normalization problem ...

https://docs.microsoft.com/en-us/office/troubleshoot/access/database-normalization-description
https://en.wikipedia.org/wiki/Database_normalization

-----Original Message-----
From: Simon Connah <simon(dot)n(dot)connah(at)protonmail(dot)com>
Sent: Tuesday, May 10, 2022 19:33
To: pgsql-novice(at)lists(dot)postgresql(dot)org
Subject: Using "object orientated" tables?

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.

Simon.