don't really understand your question/requirement. for example, any performance consideration? but I'll try to answer I think the logical deisgn would be to build a new table, and only store the daily recoomendation list, with forigen key referrance to the main table. if performance is an issue, I would actually copy the full contents of the fields to the recommendation table and do you need to keep track of the history of the "recommended"?
【在 a*******t 的大作中提到】 : don't really understand your question/requirement. for example, any : performance consideration? : but I'll try to answer : I think the logical deisgn would be to build a new table, and only store the : daily recoomendation list, with forigen key referrance to the main table. : if performance is an issue, I would actually copy the full contents of the : fields to the recommendation table : and do you need to keep track of the history of the "recommended"?
x*e
4 楼
Assail got your key. No matter what you need, 专门用一个field来标记 won't be a good idea. IF you want to do so, you can build a view for the recommended, and add the column you want into the view. You will keep the ref integraty and the performance in your mind. Also, for the recommended history, in case you want, you want to use the dimentional/fct model, the dimentional table will be your book table, and keep the id with the history to build the transctional history fct table.