News for hackers. Stuff that matters.
Re:Common mistakes in PostgreSQL by typenil on Friday May 03, 2019 @09:20AM (#19818128)
Funny how an article popped up on HN last week that mentioned table inheritance in a list of obscure Postgres features you should try out.

If I'd read this first, I wouldn't have wasted Saturday finding out for myself why you shouldn't use it.

Re:Common mistakes in PostgreSQL by perlgeek on Friday May 03, 2019 @02:51PM (#19821188)
... or if you had read the HN comments on that article: https://news.ycombinator.com/item?id=19768864 :-)
Re:Common mistakes in PostgreSQL by zeroimpl on Friday May 03, 2019 @08:31PM (#19823454)
If they supported foreign keys, I’m pretty sure I’d have used it many times. It seems like a good way to efficiently represent multiple distinct types which have some shared columns and some non-shared columns.
Re:Common mistakes in PostgreSQL by elsurudo on Saturday May 04, 2019 @03:30PM (#19828687)
I recently used table inheritance to great effect on a project, so I wouldn't write it off completely. My use-case was a bit different as it involved zero-downtime data imports from separate sources (concurrently), but it proved a great tool for the job.
Re:Common mistakes in PostgreSQL by hawaiian on Friday May 03, 2019 @08:45PM (#19823512)
I find how it's dismissed as a fad pretty humorous and actually a bit insightful.

>Table inheritance was a part of a fad wherein the database was closely coupled to object-oriented code. It turned out that coupling things that closely didn't actually produce the desired results.