WEBVTT

00:00:01.905 --> 00:00:04.563 align:middle line:84%
The next thing,
renaming columns--

00:00:04.563 --> 00:00:06.105 align:middle line:84%
so if you don't like
the column name,

00:00:06.105 --> 00:00:08.025 align:middle line:84%
if you didn't like
ZUSER or ZTIMESTAMP,

00:00:08.025 --> 00:00:10.365 align:middle line:90%
ZMESSAGE, change it.

00:00:10.365 --> 00:00:12.075 align:middle line:84%
You can change it
and say, OK, you

00:00:12.075 --> 00:00:20.552 align:middle line:84%
know what, ZUSER as quotes
user quote comma, same thing.

00:00:20.552 --> 00:00:21.885 align:middle line:90%
So I'm going to do this for you.

00:00:21.885 --> 00:00:23.760 align:middle line:84%
And I'm actually OK with
how these are named,

00:00:23.760 --> 00:00:25.425 align:middle line:84%
but I'm going to
pretend I'm not.

00:00:25.425 --> 00:00:35.565 align:middle line:84%
I'm going to say AS Warning
path AS File Path, whatever

00:00:35.565 --> 00:00:38.595 align:middle line:90%
you want it to be.

00:00:38.595 --> 00:00:45.502 align:middle line:84%
And then AS Update Time-- no
comma because from is there--

00:00:45.502 --> 00:00:46.585 align:middle line:90%
notice how it all changed.

00:00:46.585 --> 00:00:49.335 align:middle line:84%
So now it says Warning,
File Path Update Time.

00:00:49.335 --> 00:00:50.685 align:middle line:90%
Excellent.

00:00:50.685 --> 00:00:53.295 align:middle line:90%
This is a Unix Epoch timestamp.

00:00:53.295 --> 00:00:55.575 align:middle line:90%
So we saw Mac in the slides.

00:00:55.575 --> 00:00:57.285 align:middle line:90%
Now we're seeing Unix Epoch.

00:00:57.285 --> 00:00:59.665 align:middle line:90%
Something that is so important--

00:00:59.665 --> 00:01:03.125 align:middle line:84%
and I would love for everyone to
write this down at this point.

00:01:03.125 --> 00:01:08.615 align:middle line:84%
Unix is going to start
with 13, 14, 15, or 16.

00:01:08.615 --> 00:01:12.575 align:middle line:84%
And what I mean by that is,
in any timestamp column starts

00:01:12.575 --> 00:01:17.345 align:middle line:90%
with 13, 14, 15, 16.

00:01:17.345 --> 00:01:23.775 align:middle line:90%
Mac starts with 3, 4, 5, or 6.

00:01:23.775 --> 00:01:25.455 align:middle line:84%
The reason I'm
telling you this--

00:01:25.455 --> 00:01:29.445 align:middle line:84%
I hope on your GIACs, you get
hit with a table and it says,

00:01:29.445 --> 00:01:31.095 align:middle line:90%
what type of timestamp is this?

00:01:31.095 --> 00:01:32.835 align:middle line:84%
Because of my
quizzing, hopefully it

00:01:32.835 --> 00:01:36.128 align:middle line:84%
takes you 5 to 10 seconds
to know the answer,

00:01:36.128 --> 00:01:37.545 align:middle line:84%
and you answer it,
which gives you

00:01:37.545 --> 00:01:39.585 align:middle line:84%
more time to look at
other questions that

00:01:39.585 --> 00:01:41.185 align:middle line:90%
could be more challenging.

00:01:41.185 --> 00:01:43.695 align:middle line:84%
You also need to know
this to write the query.

00:01:43.695 --> 00:01:45.705 align:middle line:90%
Because no one can read that.

00:01:45.705 --> 00:01:52.485 align:middle line:84%
No one knows what that means
when you see 497800782.474.

00:01:52.485 --> 00:01:53.865 align:middle line:90%
Not readable.

00:01:53.865 --> 00:01:57.015 align:middle line:84%
You have to understand how to
do the math conversion to make

00:01:57.015 --> 00:01:58.305 align:middle line:90%
that a readable timestamp.

00:01:58.305 --> 00:02:04.365 align:middle line:84%
How we handle Mac is different
than how we handle Unix.

00:02:04.365 --> 00:02:07.495 align:middle line:84%
Now, for Unix, what you
want to do is count.

00:02:07.495 --> 00:02:13.685 align:middle line:84%
So we have 1, 2, 3,
4, 5, 6, 7, 8, 9, 10.

00:02:13.685 --> 00:02:17.135 align:middle line:90%
Unix Epoch, 10 digits in length.

00:02:17.135 --> 00:02:20.555 align:middle line:90%
Unix Epoch millisecond 13.

00:02:20.555 --> 00:02:22.895 align:middle line:84%
So if I were you right now,
I would get out my notebook,

00:02:22.895 --> 00:02:30.665 align:middle line:84%
and I would write Mac timestamp
start with 3, 4, 5, or 6.

00:02:30.665 --> 00:02:33.945 align:middle line:90%
The column name does not matter.

00:02:33.945 --> 00:02:39.915 align:middle line:84%
Unix Epoch starts
with 13, 14, 15, 16,

00:02:39.915 --> 00:02:41.745 align:middle line:90%
and it's 10 digits in length.

00:02:41.745 --> 00:02:46.885 align:middle line:84%
Unix Epoch millisecond
13, 14, 15, 16

00:02:46.885 --> 00:02:49.455 align:middle line:90%
and is 13 digits in length.

00:02:49.455 --> 00:02:51.353 align:middle line:84%
If you have your
little PDF cheat sheet,

00:02:51.353 --> 00:02:52.145 align:middle line:90%
you can print that.

00:02:52.145 --> 00:02:52.835 align:middle line:90%
Write it on it.

00:02:52.835 --> 00:02:55.535 align:middle line:84%
Just write it down until
you've exhausted it,

00:02:55.535 --> 00:02:58.313 align:middle line:84%
and it's so sharp in your
mind that you can just count.

00:02:58.313 --> 00:02:59.855 align:middle line:84%
I'm to the point
now where I can look

00:02:59.855 --> 00:03:02.675 align:middle line:84%
I'm like, yeah, that's
more than 10 milliseconds.

00:03:02.675 --> 00:03:04.472 align:middle line:84%
That way you're not
guessing on the math.

00:03:04.472 --> 00:03:05.930 align:middle line:84%
Because this is
what's coming next.
