userhierarchy table schema

[anonymoussprocket]

Retail users will be sub-accounts of some house userid. PK on this table would be userid+managerid.

Column	Data Type	Description
userid	numeric	FK into users table
managerid	numeric	FK into users table (userid)
effectivedate	timestamp	record date

[vishakh]

What is a retail user? What is a 'house userid'?

[anonymoussprocket]

A retail user is one who signed up straight from the website w/o referral or hand-holding. A non-corp user with just one account.

A house user id is a catch-all to allow enforcement of the not null condition on the manager id field. It would be an account Cryptonomic controls.

[vishakh]

How is the record for the house user ID inserted?

[ivanopagano]

Wish list:
manager is an abused term, I'd love if we could better frame the role with a meaningful name, taken from the real-life counterpart domain language.

I find manager simply doesn't convey much about the actual meaning of this relationship

[anonymoussprocket]

house user id will be baked into the DB init script.

managerid can be called parentid

[ivanopagano]

Do you imagine the hierarchy tree to be 2-level deep or more complex?

Up to now I can imagine

• Cryptonomic house user catch-all at the same level with other organizations;
• one level deeper, actual individual user accounts

but I might be framing it all wrong