博客和评论使用哪个唯一 ID？

发布于 2024-12-06 05:24:46 字数 683 浏览 0 评论 0原文

假设我有两种类型的用户，一个作者和一个读者，每个用户都存储在与主帐户表相关的关系表中，如下所示

TABLE Accounts {
    id
    email
    password
    salt
    created
    modified
}

TABLE reader {
    id
    user_id
    ...
}

TABLE author {
    id
    user_id
    ...
}

：作者帖子博客，我应该使用作者表中的唯一 ID 还是帐户表中的唯一 ID 来标记博客？读者评论也是如此 - 我应该使用读者表唯一 ID 还是帐户表唯一 ID 来标记评论？

所以，基本上要么：

TABLE Blogs {
    id
    author_id
}

要么

TABLE Blogs {
    id
    account_id
}

哪个稍后不太可能反击？

原文

This is a question that arose from the consequences of another question here: Is it better to have two separate user tables or one?

Assuming I have two types of users, an Author and a Reader, each stored in relational tables keyed to a main Accounts table like so:

TABLE Accounts {
    id
    email
    password
    salt
    created
    modified
}

TABLE reader {
    id
    user_id
    ...
}

TABLE author {
    id
    user_id
    ...
}

When an Author posts a blog, should I tag the blog with the unique id from the Authors table, or the unique id from the Accounts table? Same goes with reader comments - should I tag the comment with the Reader table unique id, or the Account table unique id?

So, basically either:

TABLE Blogs {
    id
    author_id
}

TABLE Blogs {
    id
    account_id
}

Which is less likely to bite back later on?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

秋意浓 2024-12-13 05:24:46

TABLE user {
    id
    email
    password
    salt
    created
    modified
}

TABLE profile {
    user_id
    age
    favorite_movie
    ... other useless stuff...
}

TABLE user_role {
    user_id
    role_id
}

TABLE role {
    id
    name (author, admin, user, subscriber, etc...)
}

TABLE blog {
    id
    user_id
    title
    text
    ...etc...
}


user HASMANY role
user HASONE profile
user HASONE blog

因此，用户可以是管理员和作者。您可以通过查看找到他们的博客
获取与此 user_id 匹配的博客。如果您有帐户类型相关字段
然后将它们全部放入“配置文件”表中。

TABLE user {
    id
    email
    password
    salt
    created
    modified
}

TABLE profile {
    user_id
    age
    favorite_movie
    ... other useless stuff...
}

TABLE user_role {
    user_id
    role_id
}

TABLE role {
    id
    name (author, admin, user, subscriber, etc...)
}

TABLE blog {
    id
    user_id
    title
    text
    ...etc...
}


user HASMANY role
user HASONE profile
user HASONE blog

So a user can be an admin, and an author. You can find their blogs by looking
for a matching blog for this user_id. If you have account type dependant fields
then place them all in the "profile" table.

回复收藏 0 原文