哪种 MySQL 模式最适合此类系统
假设有一个类似于 Netflix 的系统，其中成员创建了一个电影愿望清单，并根据他们的计划类型，将列表中的一部、两部或多部电影变成订单，那么以下哪一种模式更有意义？
存储以下列的控制表：
controls(memberid, currentMoviesAtHome, movieAtHomeLimit, currentMonthlyMovies, MonthlyMoviesLimit)
用户实际上并不决定何时创建订单因为这取决于他们的帐户控制。日常功能将检查客户及其控件，并选择 currentMoviesAtHome currentMoviesAtHome currentMoviesAtHome currentMoviesAtHome currentMoviesAtHome currentMoviesAtHome currentMoviesAtHome movieAtHomeLimit 和当前每月电影 < MonthlyMoviesLimit ...
链接到
plans计划表的单独accounts表：帐户（memberid、planid、currentMoviesAtHome、currentMonthlyMovies）
plans(planid, movieAtHomeLimit, MonthlyMoviesLimit)
Assuming a system similar to Netflix where members create a wish list of movies and, based on their type of plan, one, two, or more of those movies in their list turn into orders, which one of the following schemas makes more sense?
A controls table storing the following columns:
controls(memberid, currentMoviesAtHome, moviesAtHomeLimit, currentMonthlyMovies, monthlyMoviesLimit)
The user does not actually decide when the order is created as that depends on their account controls. A daily function will go through the customers and their controls and choose ones where currentMoviesAtHome < moviesAtHomeLimit AND currentMonthlyMovies < monthlyMoviesLimit ...
A separate
accountstable linked to aplansplans table:accounts(memberid, planid, currentMoviesAtHome, currentMonthlyMovies)
plans(planid, moviesAtHomeLimit, monthlyMoviesLimit)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
第二个选项具有
ACCOUNTS和PLANS表，已标准化，因此这是我的建议。此外，这些表：
MOVIESWISHLISTMOVIES.movie_id的外键）ACCOUNTS.account_id的外键）is_onsite 将是一个布尔值确定电影是否已发送给客户端。如果有，值应设置为 1。使用该值求和即可了解帐户是否达到或低于其计划限额。返回视频时，仅删除 is_onsite 设置为 1 的行。
The second option, having the
ACCOUNTSandPLANStables, is normalized so it would be my recommendation.Additionally, these tables:
MOVIESWISHLISTMOVIES.movie_id)ACCOUNTS.account_id)The is_onsite would be a boolean to determine if the movie has been sent to the client. If it has, value should be set to 1. Use this to sum to know if the account is at or under their plan limit. When videos are returned, only delete the rows that have is_onsite set to 1.
这并不能回答您的问题，但我想我会提到您的设计不是最佳的。正如您上面所描述的，您最好根据需要决定要做什么，而不是进行轮询；也就是说，在应用程序的使用过程中，显然会有一段时间限制值会被更新。您应该做的是当时触发某种事件并消耗该事件，以决定是否发送另一部电影。
每天的投票不会扩大规模。
触发和处理事件不仅会更快，而且从长远来看也更容易维护。祝你好运。
This doesn't answer your question but I thought I'd mention that your design is suboptimal. Rather than polling, as you describe above, you're much better off deciding what to do on-demand; that is, there will obviously be a time in your application's use where the limit values will be updated. What you should do is fire some kind of event at that time and consume the event that will decide whether or not to send out another movie.
Polling on a daily basis will not scale.
Firing and handling an event will not only be faster but it will be easier to maintain in the long run. Good luck.