Laravel QueryBuilder to DB::select

I’ve got an issue with a bottleneck in Laravel eloquent. When running the logic to build the query it’s very quick and simple while using eloquent, however, when it finally comes to use $query->get() (due to the number of rows, and the number of relational rows), it grinds to a halt and hits max execution time. I obviously don’t want to just increase the time… And I’d prefer not to re-write all my functions to use raw queries (although I will, if I have to).

My question is, is there a way to pass a QueryBuilder sql command to DB::select or DB::raw.

I know you can use $query->toSql() – but I’m lacking the data bound values, if I could get those, I could solve this in seconds.

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

You can get bindings from a query builder by calling $query->getBindings().


All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

0 0 votes
Article Rating
Subscribe
Notify of
guest

0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x