The better business case for a PR like this is if it also enables the end users to write slightly better and faster code than what is already provided by the sql like methods. I would therefore understand why someone would avoid these except methods for performance reason. To me this is highly inefficient as it will take 2 queries to do a job that would have otherwise been done by one query and provided better performance. Calling ->except() on some task inside that route will require me to query the user model first with the current id and then pass it to the except method which will do another query.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |