1
00:00:04,990 --> 00:00:05,710
Welcome back.

2
00:00:06,190 --> 00:00:12,340
We've added the current TimingsContract class and modified our database code to create the view.

3
00:00:12,340 --> 00:00:18,340
The next step is to change the content provider to allow queries against the new view.

4
00:00:18,490 --> 00:00:21,150
We've used constants for the uriMatcher.

5
00:00:21,280 --> 00:00:34,300
So I'll start by creating a constant for the current timing.

6
00:00:34,370 --> 00:00:39,590
Now that we've got a new value to match, we need to update the uriMmatcher function.

7
00:00:50,720 --> 00:00:53,740
If the uri's for our new current timing view,

8
00:00:53,840 --> 00:00:56,200
the matcher will return 300.

9
00:00:56,420 --> 00:01:00,230
We should return the correct MIME type in the getType function.

10
00:01:10,380 --> 00:01:13,600
I talked about MIME types back in section 12.

11
00:01:13,620 --> 00:01:19,770
It's easy to forget to update them, because we're not using the MIME types. But they are a part of the

12
00:01:19,770 --> 00:01:25,260
content provider API, so we should make sure that we return something valid.

13
00:01:25,290 --> 00:01:26,200
All right.

14
00:01:26,310 --> 00:01:31,800
The final change in here is to use the current timing view in the query function

15
00:01:42,020 --> 00:01:43,310
okay.

16
00:01:43,420 --> 00:01:50,330
That's all the background work completed. Our classes can now handle the new current timing view.

17
00:01:50,500 --> 00:01:55,140
We just need to use it in the TaskTimerViewModel class.

18
00:01:55,160 --> 00:01:55,570
I'll write

19
00:01:55,570 --> 00:01:59,480
the code for that, and test it all, in the next video.

20
00:01:59,530 --> 00:02:00,130
See you there.