Thread: Database Desing -- Help Needed!

First thing I would do is read on database normalization. That will help with number 1. #2. You will be fine. Forums with hundreds of thousands of messages work perfectly fine on mysql. Holding the information will not slow the server at all. The queries could slow if not properly indexed, but the information is only accessed as needed, so this is not an issue. #3 the data will technically...

Hi, I have some new questions I am now working to make the database with each Form. But I am now stuck on how to make some tables. Here I have a image about what relations and tables I already have. It's only a beginning: Well you have with a maffia website always times before you can do a crime again or the time you need to spend in jail. Well do you think it is usefull to put ...

Hi, I have some new questions I am now working to make the database with each Form. But I am now stuck on how to make some tables. Here I have a image about what relations and tables I already have. It's only a beginning: Well you have with a maffia website always times before you can do a crime again or the time you need to spend in jail. Well do you ...

It all depends on the normalization. However. For family members. If everyone has a set number, then you dont really ned a different table. But if even one person has a different number of family members, you need a separate table for that. Especially if people can share family members. Currently your DB setup is not relational. You don't have foreign keys to allow for cross referencing...

It all depends on the normalization. However. For family members. If everyone has a set number, then you dont really ned a different table. But if even one person has a different number of family members, you need a separate table for that. Especially if people can share family members. Currently your DB setup is not relational. You don't have foreign keys to ...

Well I don't need a Family Member table then, you can just search the member list with the correct FID that connects to the familyID. But I don't quite understand what you mean that my DB setup is not relational. For the Car Table, I think it is not necessary to put in each table the carID. Because when I want to show the list of cars that a specific user has. I can just search the ...

True about being able to look at the cars table. But then you need to do one search to get the user data and a second one for the cars. You want to do it in one search you want SELECT * FROM users, cars WHERE cars.user_id = user.user_id AND user.user_id = 3 This will give you everything about the user including their cars. What you have is SELECT * FROM users WHERE user....

Do you mean like this? And do I need to make cross referencing for every table?? And for the family setup why was this wrong? Because I didn't mean with family, specific members related to each other like uncle etc. But I meant it like a clan:P

Do you mean like this? And do I need to make cross referencing for every table?? And for the family setup why was this wrong? Because I didn't mean with family, specific members related to each other like uncle etc. But I meant it like a clan:P

Yeah. I would. Its called foreign keys. It is what makes it so efficient. For the family. If the "clan or gang" is other members. Then you dont need to store anything aside from the user_id and the relatedTo_id You were storing other information such as their money etc. That is all stored in the user table. So you dont need it twice. You should never need repeated information in ...