The latest readings
table his holds a time, a document, a point's id and a value
— tree columns come from the point
| time | doc | rid | name | val | unit |
|---|
A rename is one write in the tree: every row of the point shows the new name at the next
query, old rows too. The table was never told.
--
Search the names the table has no name to search
| time | rid | name | val | unit |
|---|
The engine finds the points whose
desc holds the text (upper or lower case
alike, contains-ci) and writes their ids into the SQL: rid IN ('L1_PT1','L2_PT1').
No point matches: IN (NULL), no row.Work orders
| wo_wid | wo | title | made | state |
|---|
The table knows an order by a number.
{wo_wid:010X} makes its id in the tree,
{wo_wid>>32:d} its line. A title the row has of its own stays
(title ?=); the others come from the tree. open in the tree reads the ids back into
numbers: ~ WO{:010X}.The SQL what main.view writes to @qry every second; the
/*xdb comments never reach the database