It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical andcannot be reasonably answered in its current form. For help clari
I开发者_运维技巧 already published an android app where you can see a list of specific objects and detailed informations about them. The list changes every day but some of the objects can appear again
For student council this year, I\'m on the \"songs\" committee, we pick the songs. Unfortunately, the kids at the dances always end up hating some of the stupid song choices. I thought I could make it
I have two entity groups. Restaurants and Users. Restaurants can be rated (1-5) by users. An开发者_如何学Pythond rating fromeach user should be retrievable.
What is the best approach to storing product ratings in a database? I have in mind the following two (simplified, and assuming a MySQL db) scenarios:
I am about to embark on a new project - a video website. Users will be able to register, and vote on videos by clicking \"like\" or \"dislike\", or something to that effect. In any event, it will be a
Let\'s say you\'re designing the DB schema for the next stack overflow and more specifically the part of the schema 开发者_开发技巧that handles question ratings.
I\'m trying to shrink this down... but can\'t figure out a way to do it. Basically am wondering if theres any way to compress it down to 5 lines or so??
I was thinking of implementing a thumbs system, but mine would require a registration thus ruling out the possibility of people voting more than once unless they create a new account to do so. So I wa
加载中,请稍侯......