#ELOQUENT ORM UPDATE#
#ELOQUENT ORM CODE#

If you would like to disable this feature simply add the $timestamps class attribute to your model and set it to false.

#ELOQUENT ORM UPDATE#

So you see, updating is performed exactly the same way as inserting except that we need to find the object that we want to update first.ĭo you remember using $table->timestamps() with in the migrations chapter to make updated_at and created_at fields? Eloquent will update these automatically for you, inserting a timestamp when an object is created and updating the updated_at field every time you save. Well I couldn't take all his mojo, that wouldn't be fair. We can't change the values on an array, we would have to loop through each one and that would make a longer example than we need! mojo = '5%' Here we use first() because we want to make sure we only get one object back. So what about updating a row? It's very similar, except we need to query for the user we want to change first. Please be careful not to let any extra information slip through when using mass-assignment as it could result in a potential security risk. If we already have a key-value array describing our friend 'Captain Sexypants' then we can either pass it as a constructor parameter to the new object, or use the mass-assignment method fill() to add him to the database. It's like the database and all that nasty SQL doesn't even exist! It's a really nice way of interacting with our rows by treating them the same as any other object in our application. This is commonly known as the Active Record design pattern. You see we simply create a new User object, set class attributes for the fields that exist (we don't need to set the ID, Eloquent handles that) and save() the object to write our changes to the database. Creating and updating objects (rows) just got a whole lot easier! name = 'Captain Sexypants' īest not to invite Captain Sexypants to our party, we won't get any action with him around. Simply flick back a chapter and mentally replace the word Fluent with Eloquent. I could cover all the query methods again for returning results, but I don't really need to. There is nothing new there, just increased clarity. You see we just used a where() chain method and get() just like we did with fluent. Whoop, lots better! The eye-candy threshold went up significantly. If you want to exclude certain fields from this array, you could add a $hidden static attribute to your Eloquent model, containing an array of all the fields to exclude. What if we would rather have our User object returned as an array? Simply call the to_array() method on any Eloquent model to receive an array instead of an object. Let's dive right in and check out the Eloquent model.

#ELOQUENT ORM CODE#

It's going to make our code look even clearer. The only difference is that we are going to be interacting with Eloquent models as results, rather than the stdObject we get back from Fluent.

You see Eloquent is an alternative to using Fluent, but it shares many of the same methods. For this portion I am going to assume that you set up your database as described in the Migrations chapter, and that you are familiar with the methods and chaining from the Fluent Query Builder chapter. Eloquent ships with Laravel, and can be used out of the box. There are many ORM solutions out there, but none as Eloquent as.

The Relational part will become clear in the relationships section. (add bass beat) The mapper part, is because we are mapping our PHP objects or classes to database tables and rows. Sounds pretty complicated right? Let's break it down a little. Please note that this chapter was written for VERSION 3 of the Laravel PHP Framework.Īn ORM is a really useful package, it stands for Object Relational Mapper.

Eloquent orm