There is a page in php for sending messages. Click send, and my official account will send messages to the people who have designated to follow the changed official account. For example, the boss sends a notice to the employees, and the employees open WeChat and receive it. How to design this kind of database so that the boss can know that it has been read
There is a page in php for sending messages. Click send, and my official account will send messages to the people who have designated to follow the changed official account. For example, the boss sends a notice to the employees, and the employees open WeChat and receive it. How to design this kind of database so that the boss can know that it has been read
Field (numeric) id message show showid
Pay attention to the Cartesian product
The focus of this question is not how to design the table. When you asked how to design the table, I guess you may be new to this area of development, and there are many questions waiting for you later.
If you only consider tables, you can make a message table to store messages, and then make a user read message table to store the status of whether the user has read it.
Does WeChat currently provide an API for "read messages"? If not, your function cannot be realized
There are restrictions on mass sending. In addition, if you specify to send, the other party must trigger an event that can trigger a reply message. Please read the development documentation of WeChat official account in detail.
The process is that when the user opens WeChat and enters the link to be read, the server finds the user information through the user's openid and sends template information to the boss's openid (WeChat template information interface: http://mp.weixin.qq. com/wiki/5/6dde9eaa909f83354e0094dc3ad99e05.html ). If you want to record specific operations, you can define a status field (0 None 1 Read 2 Pushed) in the notification table to follow up the status of the notification
There is a switch in the WeChat background that uploads geographical location information every 5 seconds after entering the chat interface.
The "read message" can be implemented less perfectly.