Member Since 2 Months Ago
4,920 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
Earned once your experience points ranks in the top 10 of all Laracasts users.
Thanks for your reply!
An instance of a model represent an entity and thus contains methods related to that one entity. I've many queries which return a collections of a model ( many records ) and i want to wrap those queries into different functions so that i can reuse them. so adding those functions in a model is a good idea or bad?
here is an example:
$flights = Flight::where('destination', 'Paris')->get();
this is just an example, i've many and much complex queries which are going to be used in several controllers. repeating same query will make code unmanageable and putting them all in model to reuse them doesn't make sense as well. so what the solution creating repositories with different numbers and types of functions for different models or else? please suggest.. thank you!
Started a new Conversation Mixing Methods For Retrieving Collections Of Products, With Methods For Instances Of One Product?
is there good alternatives of mixing methods for retrieving collections of Products, with methods for instances of one Product in a model?
Thank you very much! in case it might be helpful for someone or might be some sane person reply that "it is not a good idea to do this and that.." i'v started using laravel lately and i too have many such questions for that i keep googling which pop-ups such "archaeological debris". And the good thing is that many are helpful.