Home/ Questions/Q 3874404
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T22:08:52+00:00

I have been creating a web app and am looking to expand. In my

  • 0

I have been creating a web app and am looking to expand. In my web app I have a table for users which includes privileges in order to track whether a user is an administrator, a very small table for a dynamic content section of a page, and a table for tracking “events” on the website.

Being not very experienced with web application creation, I’m not really sure about how professionals would create systems of databases and tables for a web application. In my web app, I plan to add further user settings for each member of the website and even a messaging system. I currently use PHP with a MySQL database that I query for all of my commands, but I would be willing to change any of this if necessary. What would be the best wat to track content such as messages that are interpersonal and also specific user settings for each user. Would I want to have multiple databases at any point? Would I want to have multiple tables for each user, perhaps? Any information on how this is done or should be done would be quite helpful.

I’m sorry about the broadness of the question, but I’ve been wanting to reform this web app since I feel that my ideas for table usage are not on par with those that experienced programmers have.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Here’s my seemingly long, hopefully not too convoluted answer to your question. I think I’ve covered most, if not all of your queries.

    For your web app, you could have a table of users called “Users”, settings table called “UserSettings” or something equally as descriptive, and messages in “PrivateMessages” table. Then there could be child tables that store extra data that is required.

    User security can be a tricky thing to design and implement. Do you want to do it by groups (if you plan on having many users, making it easier to manage their permissions), or just assign individually due to a small user base? For security alone, you’d end up with 4 tables:

    Users
UserSettings
UserGroups
UserAssignedGroups

    That way you can have user info, settings, groups they can be assigned to and what they ARE assigned to separated properly. This gives you a decent amount of flexibility and conforms to normalization standards (as mentioned above by DrSAR).

    With your messages, don’t store them with the username, but rather the User ID. For instance, in your PrivateMessages table, you would have a MessageID, SenderUserID, RecipientUserID, Subject, Body and DateSent to store the most basic info. That way, when a user wants to check their received messages, you can query the table saying:

       SELECT * FROM PrivateMessages WHERE RecipientUserID = 123556

    A list of tables for your messages could be as such:

    PrivateMessages
MessageReplies

    The PrivateMessages table can store the parent message, and then the MessageReplies table can store the subsequent replies. You could store it all in one table, but depending on traffic and possibly writing recursive functions to retrieve all messages and replies from one table, a two table approach would be simplest I feel.

    If I were you, I’d sit down with a pencil and paper, and write down/draw what I want to track in my database. That way you can then draw links between what you want to store, and see how it will come together. It helps me when I’m trying to visualise things.

    • 0