30 Days to Learn Laravel, Ep 12 - Pivot Tables and BelongsToMany Relationships
HTML-код
- Опубликовано: 2 окт 2024
- The next key Eloquent relationship type to understand is belongsToMany(). You will reach for this type whenever you're working with pivot tables. We'll use the example of jobs and tags to illustrate the basic concept.
Watch Full Series on: laracasts.com/...
Watch thousands of videos, track your progress, and participate in a massive Laravel community at Laracasts.com.
Laracasts: laracasts.com
Laracasts Twitter: / laracasts
Jeffrey Way Twitter: / jeffrey_way
Wow you really make it easy to understand compared to other sources. Continue the good work.
I really love laracast because even though I've been using laravel for 3 years, I still learn new things and tips in this series. Great job!
Definitely, me too, I've been doing laravel for over 3 years but I've never really known how relationships, pivot tables actually work, and now I feel like a beginner 😅
Really good video's. But I prefer edgeDB when it comes to relationships (and ORM's in general). So much simpler. So much less code to write! Just learning Laravel to get a job.
Laravel is life
Pheww. Everytime I finish an episode I feel like I level up 10 times
FYI - Tried the rollback and migration in the VSC terminal, and got the following error:
"The token '&&' is not a valid statement separator in this version."
Tried again in the cmd window and it was fine
You saved me, thanks!
❤❤❤
Hi! Should pivot table names singular? e.g., job_tag instead of job_tags? I encountered a constraint violation error when I unknowingly job_tags.
the convention for pivot tables is to name it accordingly to the model names (singular_singular), in alphabetical order. so a pivot for Posts (model Post) and Categories (model Category) would be category_post.
@@renatofrota I see. That makes sense. Thanks!
Best best
There is a little something I have trouble understanding.
You write, as relatedPivotKey and foreignPivotKey (in the Job/Tag models) for it to be "job_listing_id".
Whereas, in your database (and everywhere else), it's clearly written "job_listings_id" with an "S" at listing. How come your query works with the table name not matching ? I tried without the S myself and it trhew an error not finding "job_listing_id" (which is normal, since in my database, just like yours, it's "job_listings_id" instead.
the table name is "job_listings" (it is what it represents: a collection of job listings) as like the "tags" table is a collection of tags. the other hand, the columns at the pivot table job_tag holds the id of a particular listing (job_listing_id, in singular form) and the id of a particular tag (tag_id, also in singular form).
nice
I've been debugging for some hours. I've checked and rechecked my code, but seems like my pivot table relationship is not similar as yours. Mine don't have the primary key for the job_listing_id and the tag_id
5:57
@@jerryjohnson5140 Is just a structure but basically when you do $table->foreignIdFor(Model Class) which is in the video is Job::class, after migration, the column will be like this job_id, but since sir Jeffrey override it, it became like this job_listing_id. if you're inside job_tags table, the job_listing_id and tag_id are FK not PK.
Maybe I miss something. You can reply your problem here so that others can also answer.
I'm gonna guess you fixed that already, but if not : It probably comes from your migration "create_tags_table" where he puts 2 create in there (4:43 timestamp). This is what generates the fields in the DB if I'm not mistaken.
If you've got it already, did you migrate:refresh ? If you did, did you CTLR + R while on TablePlus to refresh the DB tables/fields ?
Cheers
Awesome