Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
if you're using a lot of joins, sub-queries or a massive data-set eloquent will most likely choke indeed, but it has its uses and is more than often acceptable, even if it adds on top of just a simple query builder:
https://stackoverflow.com/a/...
https://codeburst.io/how-to-use-lar...
https://reddit.com/r/PHP/... -
Wombat105826y@JoshBent good resources but still for middle sized queries I am faster, more precise and more efficient when I just write the raw SQL. Maybe it's me not knowing Eloquent that well, bit for now I can say it bur s more of my time than ot saves.
-
@Divisionbyzero you'll be screaming once you have to e.g. change a table and have a rather big system to go through, eloquent does help with a lot of things, especially readability and OOP.
-
@Divisionbyzero implementing proper flow and code health is never bad in small applications either 😉
-
These links might help mate 😀
- https://hackernoon.com/eloquent-rel...
- https://laracasts.com/series/...
- https://laracasts.com/series/...
- https://courses.serversforhackers.com/... -
cursee171596yAnd using Laravel Debugbar package helped me a lot. It can show how many queries are running on a page.
-
@Divisionbyzero why do you need to involve your dead grandma? 😛 She's resting in peace
Related Rants
Eloquent is so fucking slow, my (dead) grandma queries faster. It takes the fucking double of time on a simple query with only one join for maybe ~200 rows... From now on I go fucking back to raw SQL in my Laravel projects. 😤
rant
laravel
orm
eloquent
benchmarks