@@ -134,12 +134,12 @@ Because it is so common to have:
(end.TIMESTAMP_USECS - start.TIMESTAMP_USECS)
--
-The above can be represented with *TIMESTAMP_USECS_DELTA* or if nanoseconds are OK, you can
+The above can be represented with *TIMESTAMP_DELTA_USECS* or if nanoseconds are OK, you can
use *TIMESTAMP_DELTA*. That is, the previous select can also be represented by:
[source,c]
--
-select start.pid, TIMESTAMP_USECS_DELTA as lat from sched_waking as start JOIN sched_switch as end ON start.pid = end.next_pid
+select start.pid, TIMESTAMP_DELTA_USECS as lat from sched_waking as start JOIN sched_switch as end ON start.pid = end.next_pid
--
@@ -40,7 +40,7 @@ enum field_type {
for (expr = (table)->fields; expr; expr = (field)->next)
#define TIMESTAMP_COMPARE "TIMESTAMP_DELTA"
-#define TIMESTAMP_USECS_COMPARE "TIMESTAMP_USECS_DELTA"
+#define TIMESTAMP_USECS_COMPARE "TIMESTAMP_DELTA_USECS"
#define EVENT_START "__START_EVENT__"
#define EVENT_END "__END_EVENT__"
#define TIMESTAMP_NSECS "TIMESTAMP"