[MUSIC]

What good is a to do list without to do items.

Without a doubt, we're gonna wanna keep our two

types of data separate, but relate them to one another.

Eloquent provides us a simple and effective way to relate our two models

as well as giving us flexible access to those relations through custom methods.

The relation of our data and the way we chart a path to

that data is where the power of Laravel will begin to show through.

We have successfully walked through creating, reading,

updating, and deleting our to do list.

So now we have our to do list, but the main

part about to do list is not even close to complete.

Which if we go to My Listings, being our first list here,.

Let's look where are our items.

We need items to actually complete.

So the next step for us is to create a new

model and relate that model to our current to do list model.

We're going to call this next model to do items.

So, the first step for us is to create our new model.

We're going to do that the same way we've done before by heading into our

vagrant, and using an artisan command to create

a new migration to create a new model.

Let's do that.

So here we are inside of our vagrant instance.

We can do a PHP artisan and then migrate and then make.

We're gonna have a name to the migration, makes perfect sense, so let's go very

verbose and say create_todo_items_table, so we now are

gonna create a table but we need to pass the create

flag because we don't have a table and we're actually gonna call

the table to do items.

So we have to do lists and now we have

to do items, so we're gonna hit enter on this.

So it certainly helps if you spell things correctly.

That is definitely not how you spell my grade.

I'm gonna hit up to get my history, go back over here and fix my spelling.

All right, let's try that again.

Okay so we created our migration, we clear our screen and head back over to

the sublime text, head into our database and look at our second migration.

So here's our migration, we're creating a to do items table.

We're adding our timestamps.

We are adding our ID for increments.

So, what are we gonna do, what do we need here?

Well, we're definitely going to need our item name so we'll add that in.

But we're also gonna need to wait to relate what item

belongs to a particular list, and that's where we get into relations.

So, let's start by adding our string in that's going to give us our name.

So go in, use table and then we're gonna

do a string again, and we're gonna call this content.

That'll be our to do list content.

We also want our to do list content to be unique,

so let's do a unique, and then we'll close that one out.

So now we're gonna add at the very least a string for content.

We've got our auto incrementing ID and our

timestamps to get are created on and updated at.

The other thing that we're gonna need here is to know when we've completed this.

It's super necessary but it could be very useful to us in the future.

Let's go ahead and add that now.

So table, and then we're gonna add a new type,

one that you haven't seen yet, called the dateTime, okay.

And then our dateTime we're gonna call completed_on [SOUND] all right.

And it's allowed to be null because it's not gonna be completed to start with

so we're gonna let it be a null value so here we're gonna use, nullable.

Close that out.

So, before we complete our migration we're gonna want

to have some sort of related table field here.

So, let's take a look at the migrations and see which one is going to work for us.

Let's head back over to the docs and do that now.

So, under the Laravel docs, inside of

the eloquent section, there is heading called relationships.

There's several relationships to describe here, one to one,

one to many, many to many, has many through polymorphic.

It can get really complicated.

For us, it's very very simple.

The item itself is definitely going to belong to a list.

But a list is going to be able to have many items.

So it's definitely going to be a one to many relationship.

So we click on one to many, and read what it says.

An example of a one to many relationship is a blog post.

So a blog post could have many comments.

So this is how we deal with the model relation.

So, here you see in our model for the post, and it's extension of eloquent.

We're going to have a function the called comments that will

return has many, and then the actual model which is comment.

So for us, let's switch over to our model.

For the actual, to do list and add in our list items.

So here, we're going to go in to our models and look at our to do list.

So here's our to do list.

We're extending eloquent and in here we're

going to create a new public function, right.

And our public function is going to be how we're going to get the item.

So we're gonna have list items.

So here are our list of items.

All right.

And then we'll go down close this out and then we're gonna put return this, to

access the current instance of the model or

this instance of TodoList and then hasMany and

it's going to have many to do items, so

we'll just say TodoItem, which TodoItem is our model.

So we're gonna need to go ahead and create our model now.

So same thing as TodoList except we're gonna do new file, PHP, actually save it.

And call it TodoItem.php.

Same thing as TodoList, so we're gonna actually just copy

all of this here, go into TodoItem, paste it in.

So everything here is right except TodoItem will be our name.

It's definitely gonna extend eloquent.

It's not gonna have ListItems.

It's actually gonna have a todoList.

All right, and then it's gonna return not hasMany, but it belongsTo

a not TodoItem, but TodoList.

Okay.

So, here we have our two models, the TodoList hasMany Todotems under ListItems.

And then we have a TodoItem which belongs to one TodoList.

So now, we've actually related our models.

Let's go back to the documentation and see what else we need to do.

So underneath Relationships, if we click on the One To One, it's gonna give

you a little bit of an explanation

here about how SQL performs the actual statement.

So here we're looking for a user where the ID is one.

So that's finding a user.

But then here, we have a relation where it has one phone, so

now it's saying, select from phones where the user_id is equal to one.

Here it's saying that it's assuming that there is a foreign key, that's

the key point here, foreign_key, that the relationship is based on the model name.

So in the case of phone, a phone will assume to have a user_id.

So in our case, if we head back over to our schema here,

we're gonna make sure that this has a not todo_items ID, but a todo_list ID.

We're gonna add that by going directly under the ID

here and doing table and then pointing to an integer.

Which, we want an ID, which is an integer, but we don't want it to auto increment and

the name of that field or name of that column is going to be todo_list ID.

So it's based off of our model name to do list, and then ID.

Close that out, and then we're going to go ahead and run our migration.

Notice that if we do a down, or go reverse in our

migration, it's just going to drop the entire to do IM's table.

Let's switch over to the terminal and run our migration.

So, php artisan migrate.

Okay, let's run our migration.

Let's look at our database, refresh, get rid of all the excess and

now if we refresh our tables, you'll see we now have to do items.

Nothing in here, but here are our columns, ID, to do

list ID, our content, the completed on, and then our typical timestamp.

So migration ran great.

Here's our to do list.

Now we just need to start by adding some items.