Jump to content

Implications of entity one-to-one relationships

Recommended Posts

OK, so that should involve:

  •  A users table, of course, that contains the height and age
  • An attributes table, with a column for the name of the attribute and unit of measure (UOM i.e years).
  • A user_attributes table with a column for user id, and attribute id, attribute's UOM value



Share this post

Link to post
Share on other sites

e.g. A custom UOM of "furlongs per fortnight" makes the top speed of your car sound very impressive.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.