a b c d 4 people
a delegate the task to b.
b delegate the task to c.
c delegate the task to d.
.
a. A-> b-> c-> d
.
how should the data table be designed?
a b c d 4 people
a delegate the task to b.
b delegate the task to c.
c delegate the task to d.
.
a. A-> b-> c-> d
.
how should the data table be designed?
because MySQL does not support storing sequential list types , of course, if the task queue a-> b-> c-> d is regarded as a string. Has
ever considered adding some additional attributes to the task , such as counting, timestamp, etc. Because the task itself should have a certain timeliness.
if you understand it correctly, it means that when a user starts to take over the task , the subsequent tasks of are visible to him .
for example, if the execution order of a task is a-b-c-d-b , you can have:
make a task transfer record table. A task can correspond to multiple transfer records. All the transfer records can be queried according to the task ID, and in ascending order according to time, the effect of a-> b-> c-> d can be obtained
. Previous: Phaser cycle interval how to write a faster and faster
Next: How to understand the wiredTiger internal cache of mongodb
1. Structure of the data table: order ID:orderid, user ID:memberid, date of order issued: order_date 2. Demand: need to query the record of orders issued from 2017 to April (orderid,memberid). If the user of the current record has placed an order b...