...
- The tuple (ts,ordering) is used as an index on this table.
- If you want your data to be displayed in proper time order, be sure to include the ORDER BY ts, ordering statement at the end of the SQL command. If not, the ordering of the output is not guaranteed and could be a little confusing. It typically comeback properly ordered by ts but not by ordering.
- To speed up queries, it is useful to include a filter of ts > "<date time>" in the WHERE clause of the SQL command, especially if you know the approximate time of the log entries you're looking for. As ts in an index this allows the system to optimize the query and not have to search over the entire dataset.
As an example query, to find the complete log for a given build I typically run the following SQL command:
Code Block |
---|
SELECT * FROM entry WHERE ts > '<known start time>' AND subId= <buildID from build table> ORDER BY ts, ordering
|
This generates 2-4 thousand lines of log entries for a typical build.