select * from task;
id |task_description |task_complete
2000000000 |A. Mow Lawn |0
2000000001 |R. Trim Hedge |0
2000000002 |I. Water Roses |0
Sqllite: Task Table
Note that the id for 'Mow Lawn' is 2000000000 which is in the user space for storing items.
select * from task_TR;
id |task_description |task_complete |ts |operation |user_id |user_ts |comment |crc
2000000000 |A. Mow Lawn |0 |2000000000 |1 |2 |279992047 |Insert Task |
2000000001 |R. Trim Hedge |0 |2000000001 |1 |2 |279992061 |Insert Task |
2000000002 |I. Water Roses |0 |2000000002 |1 |2 |279992072 |Insert Task |
Sqllite: Task Transaction Table
Note that the timestamp for 'Mow Lawn' is 2000000000 which is in the user space for storing items.
select * from task;
id |task_description |task_complete
1 |A. Mow Lawn |0
2 |R. Trim Hedge |0
3 |I. Water Roses |0
Note that the id for 'Mow Lawn' has been changed to 1 since the server has returned a consecutive valid id.
Sqllite: Task Table
select * from task_TR;
id |task_description |task_complete |ts |operation |user_id |user_ts |comment |crc
1 |A. Mow Lawn |0 |2000000000 |1 |2 |279992047 |Insert Task |
2 |R. Trim Hedge |0 |2000000001 |1 |2 |279992061 |Insert Task |
3 |I. Water Roses |0 |2000000002 |1 |2 |279992072 |Insert Task |
Sqllite: Task Transaction Table
select * from water_line;
water_ts |water_table_id |water_state |water_error
2000000000 |1000 |11 |0
2000000001 |1000 |11 |0
2000000002 |1000 |11 |0
Sqllite: Water Line Table
The WATER_STATE=11 which is CLIENT_SENT.
select * from task;
+----+------------------+---------------+
| id | task_description | task_complete |
+----+------------------+---------------+
| 1 | A. Mow Lawn | 0 |
| 2 | R. Trim Hedge | 0 |
| 3 | I. Water Roses | 0 |
+----+------------------+---------------+
3 rows in set (0.002 sec)
MySql: Task Table
select * from task_TR;
+----+------------------+---------------+----+-----------+---------+-----------+-------------+------+
| id | task_description | task_complete | ts | operation | user_id | user_ts | comment | crc |
+----+------------------+---------------+----+-----------+---------+-----------+-------------+------+
| 1 | A. Mow Lawn | 0 | 5 | 1 | 2 | 279992047 | Insert Task | NULL |
| 2 | R. Trim Hedge | 0 | 6 | 1 | 2 | 279992061 | Insert Task | NULL |
| 3 | I. Water Roses | 0 | 7 | 1 | 2 | 279992072 | Insert Task | NULL |
+----+------------------+---------------+----+-----------+---------+-----------+-------------+------+
3 rows in set (0.000 sec)
MySql: Task Transaction Table
select * from water_line;
+----------+----------------+-------------+-------------+
| water_ts | water_table_id | water_state | water_error |
+----------+----------------+-------------+-------------+
| 1 | 105 | 1 | 0 |
| 2 | 110 | 1 | 0 |
| 3 | 105 | 1 | 0 |
| 4 | 110 | 1 | 0 |
| 5 | 1000 | 0 | 0 |
| 6 | 1000 | 0 | 0 |
| 7 | 1000 | 0 | 0 |
+----------+----------------+-------------+-------------+
7 rows in set (0.000 sec)
MySql: Water Line Table
The water_line table refers to all of the transactions entered into the database so far.
For water_ts=5 the water_state=0 which is SERVER_PENDING, this means the item has not been approved yet and will not be sent to user phones until approval.