We should forget about small efficiencies, say about 97% of the time:
premature optimization is the root of all evil.
On Aug 14, 4:21 pm, MK Z v5s12.msc...@gmail.com wrote:
Hi,
Thanks for your reply. The category is not related to the group - category
holds value like Science/Tech/Music while
There does not seem to be any need for a table with forumcategoryid
and forumcategoryid. When a user creates a category/group, you have to
update the corresponding category table/group table. As you have
suggested, since the application is small it is far easier to handle
issues, including column
Hi,
Thanks for your reply. The category is not related to the group - category
holds value like Science/Tech/Music while Group stores value like
Teens/Kids/Adult. The reason I have these two fields I want to be able to
sort the forum according to category and follow by group. So in the forum
Recommended beginner's reading:
http://en.wikipedia.org/wiki/Database_normalization
On Aug 7, 11:49 pm, MK Z v5s12.msc...@gmail.com wrote:
Hello.
I need some help. Assuming I have three tables/objects: forum, forum
category, forum group.
Forum - stores all topics posted by user. This
Given that the target GAE datastore should be optimised for reads, since
writes are expensive, normalization of data is by no means the way to go.
Are Categories and Groups joined in any way? i.e. Has a specific Category
got a set of groups, or the other way around? If not, then storing the
