Messaging system database schema

14,342

Solution 1

I don't see much to complain about :) I'd probably cache the last modification date on the conversations table so that a list of "unread" conversations can be displayed quickly. This date would be updated each time a message is posted on the conversation.

Solution 2

I would have put the subject field on the conversation table. Putting it on every single message looks redundant. Also, I'd save the creation time and the author user id of the conversation in its table.

Share:
14,342
RS7
Author by

RS7

Updated on June 04, 2022

Comments

  • RS7
    RS7 almost 2 years

    I'm trying to implement a messaging system in PHP and MySQL but I'm having some trouble deciding on how I should do the tables and queries.

    What would be the best approach for a system that allows for multiple participants? I'm thinking I'd probably need 3 tables (aside from an users table).

    Something like

    Conversation
    ------------
    id
    
    Messages
    --------
    id
    conversation_id
    from_id
    subject
    message
    from_timestamp
    
    Participants
    ------------
    conversation_id
    user_id
    last_read_timestamp
    

    The way it is setup I'd have to check for read messages by the timestamp instead of ticking off each message. I'd also be able to add participants at any time.

    What do you guys think?

    Thanks in advance.