3ll0

3ll0

Member Since 3 Years Ago

Experience Points 175
Experience Level 1

4,825 experience to go until the next level!

In case you were wondering, you earn Laracasts experience when you:

  • Complete a lesson — 100pts
  • Create a forum thread — 50pts
  • Reply to a thread — 10pts
  • Leave a reply that is liked — 50pts
  • Receive a "Best Reply" award — 500pts
Lessons Completed 1
Lessons
Completed
Best Reply Awards 0
Best Reply
Awards
  • start-engines Created with Sketch.

    Start Your Engines

    Earned once you have completed your first Laracasts lesson.

  • first-thousand Created with Sketch.

    First Thousand

    Earned once you have earned your first 1000 experience points.

  • 1-year Created with Sketch.

    One Year Member

    Earned when you have been with Laracasts for 1 year.

  • 2-years Created with Sketch.

    Two Year Member

    Earned when you have been with Laracasts for 2 years.

  • 3-years Created with Sketch.

    Three Year Member

    Earned when you have been with Laracasts for 3 years.

  • 4-years Created with Sketch.

    Four Year Member

    Earned when you have been with Laracasts for 4 years.

  • 5-years Created with Sketch.

    Five Year Member

    Earned when you have been with Laracasts for 5 years.

  • school-session Created with Sketch.

    School In Session

    Earned when at least one Laracasts series has been fully completed.

  • welcome-newcomer Created with Sketch.

    Welcome To The Community

    Earned after your first post on the Laracasts forum.

  • full-time-student Created with Sketch.

    Full Time Learner

    Earned once 100 Laracasts lessons have been completed.

  • pay-it-forward Created with Sketch.

    Pay It Forward

    Earned once you receive your first "Best Reply" award on the Laracasts forum.

  • subscriber-token Created with Sketch.

    Subscriber

    Earned if you are a paying Laracasts subscriber.

  • lifer-token Created with Sketch.

    Lifer

    Earned if you have a lifetime subscription to Laracasts.

  • lara-evanghelist Created with Sketch.

    Laracasts Evangelist

    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.

  • chatty-cathy Created with Sketch.

    Chatty Cathy

    Earned once you have achieved 500 forum replies.

  • lara-veteran Created with Sketch.

    Laracasts Veteran

    Earned once your experience points passes 100,000.

  • 10k-strong Created with Sketch.

    Ten Thousand Strong

    Earned once your experience points hits 10,000.

  • lara-master Created with Sketch.

    Laracasts Master

    Earned once 1000 Laracasts lessons have been completed.

  • laracasts-tutor Created with Sketch.

    Laracasts Tutor

    Earned once your "Best Reply" award count is 100 or more.

  • laracasts-sensei Created with Sketch.

    Laracasts Sensei

    Earned once your experience points passes 1 million.

  • top-50 Created with Sketch.

    Top 50

    Earned once your experience points ranks in the top 50 of all Laracasts users.

18 Oct
3 years ago

3ll0 left a reply on Pivot Or Polymorphism?

Thanks, that led me to the right track after some testing.

17 Oct
3 years ago

3ll0 left a reply on Pivot Or Polymorphism?

Makes sense so far, will give it a try.

Now one last thing I am stuck on with this construct. Let's say I have tables and models like these.

tool
- name

tool_one
- parent_tool_id **(tool table)**
- name

calls
- model_id **(e.g. App\ToolOne::first()->id)**
- model_type **(e.g. App\ToolOne)**
- some_column
<?php

namespace App;

class Tool extends Model
{
    public function calls()
    {
        return $this->hasManyThrough(Call::class, ToolOne::class);
    // This would also need ToolTwo/Three/Four, pretty much merge all Calls from all 4 Tools
    }
}

The issue is that there is no calls.tool_*_id with this construct.

The Tool Model would pretty much be a Collector which should give access to all Tool Calls and Views through the 5 Tool* Models.

So how would I merge and access the relations of ToolOne/two/Three/Four through a "Tool Collector" Model with the advised setup of polymorphism and meta data? Could I store a parent_tool_id in the calls_meta table and use it within the model for a hasMany relationship?


Idea how it should work

class Tool extends Model
{
    public function calls()
    {
        return $this->hasMany(Call::class, 'parent_tool_id'); // This does not work, it doesn't check for the parent_tool_id in meta_data.parent_tool_id in the Call class
    }
}

class Call extends Model
{
    use \Kodeine\Metable\Metable;

    public function tool()
    {
        return $this->morphTo();
    }

    public function parentTool()
    {
        return $this->belongsTo(Tool::class, 'parent_tool_id'); // this part works, the parent_tool_id is taken from meta_data.parent_tool_id
    }
}

If the hasMany with the parent_tool_id from meta_data.parent_tool_id would work this would be exactly the setup I need.

16 Oct
3 years ago

3ll0 left a reply on Pivot Or Polymorphism?

All tools are completely different but the Calls and Views tables aren't that different.

The Calls and Views tables have about 10 columns each and the *_calls and *_views tables have 2-3 columns that are specific to the tool for which the table is. That is why I am using Pivot tables at the moment since I can store the shared data in the Calls and Views and create an entry on the Pivot table with the tool-specific extra columns.

3ll0 started a new conversation Pivot Or Polymorphism?

I am working on a side-project which has 4 kinds of Tools/Widgets, each has Calls and Views. All Calls and Views contain the same data for about 80%.

The other 20% are data that differs between each tool which is why I am working with pivot tables at the moment. Meaning I store the 80% that is shared data in the Calls and Views and the other 20% go into the tool_one_calls for example.

This works fine and keeps everything neat and clean but I thought about polymorphism which would remove the *_calls and *_views tables. The problem I then see is that there are like 3-4 empty columns in most cases since the columns from tools_two,_three,_four would be empty if the Model saved would be a tool_one.

So would Pivot tables or using Polymorphism be the right choice for this case?


The table names at the moment.

tool_one
tool_two
tool_tree
tool_four

calls
tool_one_calls
tool_two_calls
tool_tree_calls
tool_four_calls

views
tool_one_views
tool_two_views
tool_tree_views
tool_four_views