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.
If I'd read this first, I wouldn't have wasted Saturday finding out for myself why you shouldn't use it.
>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.