> No, that kind of "extension table" is a well-known antipattern being fragile, unscalable, and denormalized.
Ok, I agree. This is the reason why I was asking :-)
> Just a table with columns for id, keyname & metadata about the key will do.
Isn't this the Entity-Attribute-Value model (which has the well known drawback of requiring a join for each attribute)?
