Lines Matching full:tables

6 contained in a consistent set of tables. It also has other features including
25 data inside, and exposing it in a set of database tables which can be queried
122 when querying tables in trace processor.
129 ## Object-oriented tables
145 different tables for each type of object. For example, we have a `track` table
147 tables "inheriting from" the `track` table.
150 for inheritance between tables for interested readers.
152 Inheritance between the tables works in the natural way (i.e. how it works in
157 NOTE: For an up-to-date of how tables currently inherit from each other as well
159 the [SQL tables](/docs/analysis/sql-tables.autogen) reference page.
165 A common question when querying tables in trace processor is: "how do I obtain
170 on the associated `track` tables.
218 ### Thread and process tables
223 The `thread` and `process` tables map `utid`s and `upid`s to threads and
232 The `thread` and `process` tables can also be joined with the associated track
233 tables directly to jump directly from the slice or counter to the information
279 when working with very large tables; a function call is required for every
282 ## Operator tables
286 In these situations, trace processor has special "operator tables" which solve
292 spans of time from two tables or views. A column (called the *partition*)
320 -- tables.
325 NOTE: A partition can be specified on neither, either or both tables. If
328 WARNING: An important restriction on span joined tables is that spans from
340 -- Both tables unpartitioned.
353 [slice table's id column](/docs/analysis/sql-tables.autogen#slice) and computes
359 [slice table](/docs/analysis/sql-tables.autogen#slice)
378 [slice table's stack_id column](/docs/analysis/sql-tables.autogen#slice) and
384 [slice table](/docs/analysis/sql-tables.autogen#slice)
404 [slice table's id column](/docs/analysis/sql-tables.autogen#slice) and
410 [slice table](/docs/analysis/sql-tables.autogen#slice)
432 [slice table's stack_id column](/docs/analysis/sql-tables.autogen#slice) and
438 [slice table](/docs/analysis/sql-tables.autogen#slice)
459 tables that take a
460 [slice table's id column](/docs/analysis/sql-tables.autogen#slice) and collect
461 all entries of [flow table](/docs/analysis/sql-tables.autogen#flow), that are
465 [flow table](/docs/analysis/sql-tables.autogen#flow) that are present in any
477 all entries of [flow table](/docs/analysis/sql-tables.autogen#flow) that are
486 all entries of [flow table](/docs/analysis/sql-tables.autogen#flow) that are
574 query tables and run metrics without requiring the `trace_processor` binary to be
768 parsing events, testing schema of tables, testing metrics etc.) and only
837 built-in tables.
839 _Answer_: Add the test to the tables/ folder.
844 Concretely, the rules for inheritance between tables works are as follows:
846 * Every row in a table has an `id` which is unique for a hierarchy of tables.