A specialized api for a common use case can pay off, but it is not obvious to me, that it does in this case. (not saying it's not). The problem with it is that people start out with that and it is not obvious to them how to scale it to composite PKs, because it needs a different API, which means they would consult docs or support channels. Named or not named is a separate question in my eyes. `primaryKey` and `foreignKey` could provide a feature to auto-generate a unique name, which would be useful in any case in my eyes.