with the new dual id system, parent relationships need to consume 2 names

[rizen]

userPk will also be userId

• schema validator must not allow userId to exist if there is a userPk
• describe output may have to list userId
• qualifiers need to convert userId into userPk
• post/put needs to accept userId as input and convert to userPk

Might be better to actually store an extra column for these relationships as an extra column. Would then just have to make sure they can only be set via userPk, and not userId.