#Doctrine eloquent laravel code#
#Doctrine eloquent laravel plus#

#Doctrine eloquent laravel code#

After the initial high of working with entities wore off, I realised that the underlying problem was still there, I was still having to add 'work arounds' here and there, and the underlying code was still ugly to look at. This worked well, and appeased my need for something different, for a while. The models were still there, but were treated as query objects that were just used to hydrate my simple data object entities. It was originally designed to be a wrapper for Eloquent, that let me return entities instead of models.

This is actually where Articulate started, hence the name Articulate. But what if I could bring the approach that I love, to Eloquent? I didn't want to write my own ORM, because ORMs are complicated and hard. While Eloquent uses the Active Record pattern, Doctrine uses the Entity Mapper pattern, something that due to my days with Java, I was instantly in love with. Doctrine, as good as it is, is a monolithic ORM that dwarfs Eloquent in comparison. The down side, also like Eloquent, is that it can do everything.

#Doctrine eloquent laravel plus#

The plus side of Doctrine, much like Eloquent, is that it can do everything. For a while, I swore by Doctrine and used it in place of Eloquent whenever I could. Doctrineĭoctrine again, is a super powerful ORM and while more complex to setup, it can simplify your life. That didn't sit well with me, so I started exploring methods to get away from this way of doing things. Sure, it's flexible enough that I can work around, and after some time digging through the masses of functionality and methods that come with every Model, I was able to find what I needed, but it all just felt a bit.dirty.Īfter a while I noticed that some of my codebases were rife with 'work arounds' (read: hacks) to achieve what I needed while still within the confines of Eloquent.

Many a time I've encountered a wall when I tried to do something with Eloquent that it absolutely didn't like. It makes the initial steps of any Laravel build easy, but at this point it has become somewhat bloated. Updates Archived How I accidentally created an ORM to avoid using Eloquent 7th August, 2018Įloquent is a well thought out powerful ORM.