Hi right now I am just developeing a complex listing for 500+
applications over 20 tables per catigory, that is going to be hosted on
my site. besides having the normal info such as: size, file name, datep
ublished, staff comments, program rateing I wanted to include user
opinions of it too.
What you described is the strategy to design good tables, called
normalizing. You will find good articles on that subject and even
whole books. There are several rules, but most only apply the
first. The others are for the real masters or the real tough data
models or performance questions.
Sie s
You would be better off having one table that contains
userid, productid, catagory, comment.
Then if you add a catagory you don't have to add a table.
You can select based on any combination of the above fields.
MeTeX wrote:
> Hi right now I am just developeing a complex listing for 500+
> app
