Implementing "Interfaces" in SQL
My latest article has just been published over at SQLTeam:
Implementing Table Interfaces
When I wrote a Table Inheritance article a few months back, the technique shown was pretty standard and straight-forward. As I was writing it, I thought it would be an interesting challenge to figure out a way to implement table interfaces as well, where different tables don't inherit from the same base class, but they still "implement" the same relations. That definitely was not as easy, and the end result isn't as clean and direct, but I hope this at least provides some ideas and at the very least it should provoke interesting comments and alternative approaches.