Jump to content

Recommended Posts

We have close to 8000 members in our database currently. I would like to try and implement an alert/message system whereby which support can post a message/alert and ALL members can view it online in their account manager when they login to the site.

 

My database design question: What would be the most efficient way to structure the database for this type of system? I would not want to post 8000 separate messages in a messages.table, but at the same time, some members may want to delete the message from their online.inbox and others may want to save it for an unknown amount of time in their online.inbox.

 

Initially I thought about a design similar to the following (simple view).

 

alerts (id,message,date,expires,active)

alerts_delete (alertid,memberid)

 

When a member doesnt want to see an alert message, the alertid & memberid is added to alerts_delete.

Link to comment
https://forums.phpfreaks.com/topic/131236-message-alert-system-design-opinions/
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.