PHP系统公告-发送通知给每个人
经常有这样的经历,就是登陆一个系统,会有一条系统消息提示,而这条消息是针对所有人的,那么程序是如何区分哪些人已经看过这条消息哪些人没看过呢?(因为没看过的人会有一个提示一直挂在页头,而看过的人这个提示会自动消失),请问这种效果用php是如何做到的,数据结构是如何设计?
回复讨论(解决方案)
首先得有一个消息列表,表里面有个是否阅读字段就行了啊
首先得有一个消息列表,表里面有个是否阅读字段就行了啊
那要是有十万个用户,有的看过了有的没看过 ,这个字段怎么标注啊?这条消息是谁发的,发给谁 表里面也都需要记录啊,这样你就可以根据每个用户的用户id去读取个人的消息了
表结构
table1:message
msg_id msg_content publish_time
table2:read
msg_id user_id read_time
发布一条系统消息 在message插入一条记录即可
如:
123 “下午休息” 1414468731
看过的人在read表中插入一条记录
123 5145 1414468745
判断是否有未读信息
select * from message where msg_id not in (select msg_id from read where user_id = 5145)
如果你对sql效率关注 可以用下面的
select * from message where message left join (select* from read where user_id = 5145 )temp on message.msg_id = temp .msg_id where temp.user_id is null;
表结构
table1:message
msg_id msg_content publish_time
table2:read
msg_id user_id read_time
发布一条系统消息 在message插入一条记录即可
如:
123 “下午休息” 1414468731
看过的人在read表中插入一条记录
123 5145 1414468745
判断是否有未读信息
select * from message where msg_id not in (select msg_id from read where user_id = 5145)
如果你对sql效率关注 可以用下面的
select * from message where message left join (select* from read where user_id = 5145 )temp on message.msg_id = temp .msg_id where temp.user_id is null;
这条消息是谁发的,发给谁 表里面也都需要记录啊,这样你就可以根据每个用户的用户id去读取个人的消息了
这是针对所有人的,所以这种推送模式不太合适
表结构
table1:message
msg_id msg_content publish_time
table2:read
msg_id user_id read_time
发布一条系统消息 在message插入一条记录即可
如:
123 “下午休息” 1414468731
看过的人在read表中插入一条记录
123 5145 1414468745
判断是否有未读信息
select * from message where msg_id not in (select msg_id from read where user_id = 5145)
如果你对sql效率关注 可以用下面的
select * from message where message left join (select* from read where user_id = 5145 )temp on message.msg_id = temp .msg_id where temp.user_id is null;
哈哈 那考虑考虑 redis
10W 用用户 需要15K内存标记用户是否发送 每条消息都是15K
1.读取消息 setbit msg_123 5415 1
2.判断是否读取 getbit msg_123 5415
消息表有内容和userid,如果userid=0,表示该消息为全局
用户表中,可以增加一个字段记录查看过的消息id,用逗号隔开,比如 1,20,123
看过一条就加一个消息id
如果消息比较频繁,可以考虑单独维护一个消息查看记录表,只有uid msgid两个字段,记录已查看
弄个表把看过的人装起来???
没有查询到的就显示给他
表结构
table1:message
msg_id msg_content publish_time
table2:read
msg_id user_id read_time
发布一条系统消息 在message插入一条记录即可
如:
123 “下午休息” 1414468731
看过的人在read表中插入一条记录
123 5145 1414468745
判断是否有未读信息
select * from message where msg_id not in (select msg_id from read where user_id = 5145)
如果你对sql效率关注 可以用下面的
select * from message where message left join (select* from read where user_id = 5145 )temp on message.msg_id = temp .msg_id where temp.user_id is null;
哈哈 那考虑考虑 redis
10W 用用户 需要15K内存标记用户是否发送 每条消息都是15K
1.读取消息 setbit msg_123 5415 1
2.判断是否读取 getbit msg_123 5415
再次谢谢你的帮助!
消息表有内容和userid,如果userid=0,表示该消息为全局
用户表中,可以增加一个字段记录查看过的消息id,用逗号隔开,比如 1,20,123
看过一条就加一个消息id
如果消息比较频繁,可以考虑单独维护一个消息查看记录表,只有uid msgid两个字段,记录已查看
没有查询到的就显示给他
恩!可以这样子试试

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Alipay PHP...

JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

Article discusses late static binding (LSB) in PHP, introduced in PHP 5.3, allowing runtime resolution of static method calls for more flexible inheritance.Main issue: LSB vs. traditional polymorphism; LSB's practical applications and potential perfo

The application of SOLID principle in PHP development includes: 1. Single responsibility principle (SRP): Each class is responsible for only one function. 2. Open and close principle (OCP): Changes are achieved through extension rather than modification. 3. Lisch's Substitution Principle (LSP): Subclasses can replace base classes without affecting program accuracy. 4. Interface isolation principle (ISP): Use fine-grained interfaces to avoid dependencies and unused methods. 5. Dependency inversion principle (DIP): High and low-level modules rely on abstraction and are implemented through dependency injection.

How to automatically set the permissions of unixsocket after the system restarts. Every time the system restarts, we need to execute the following command to modify the permissions of unixsocket: sudo...

Session hijacking can be achieved through the following steps: 1. Obtain the session ID, 2. Use the session ID, 3. Keep the session active. The methods to prevent session hijacking in PHP include: 1. Use the session_regenerate_id() function to regenerate the session ID, 2. Store session data through the database, 3. Ensure that all session data is transmitted through HTTPS.

Static binding (static::) implements late static binding (LSB) in PHP, allowing calling classes to be referenced in static contexts rather than defining classes. 1) The parsing process is performed at runtime, 2) Look up the call class in the inheritance relationship, 3) It may bring performance overhead.

How to debug CLI mode in PHPStorm? When developing with PHPStorm, sometimes we need to debug PHP in command line interface (CLI) mode...
