Chapters

28 Chapters | 2:24:59 |

01

Give me Clean URL Strings (slugs!)

5:39
02

DoctrineExtensions: Sluggable

4:59
03

Refactoring Carefully

3:41
04

ManyToMany Relationship

5:18
05

Inserting into a ManyToMany

5:27
06

Fetching Items from a ManyToMany Collection

3:45
07

ManyToMany: The Inverse Side of the Relationship

6:45
08

Removing a ManyToMany Item

5:16
09

Hooking up the Scientist Removal JavaScript

2:50
10

ManyToMany & Fixtures

3:30
11

Joining Across a ManyToMany + EXTRA_LAZY Fetch

5:34
12

EntityType Checkboxes with ManyToMany

5:39
13

Saving the Inverse Side of a ManyToMany

4:03
14

Form by_reference + Adder and Remover

4:40
15

Synchronizing Owning & Inverse Sides

4:03
16

ManyToMany with Extra Fields

8:20
17

Join Entity App Refactoring

2:40
18

Using the new OneToMany Collections

5:46
19

Embedded Form: CollectionType

6:36
20

Collection Delete & allow_delete

4:49
21

Deleting an Item from a Collection: orphanRemoval

5:14
22

CollectionType: Adding New with the Prototype

7:07
23

Adding to a Collection: Cascade Persist

6:04
24

Embedded Form Validation with @Valid

5:05
25

Customizing the Collection Form Prototype

5:56
26

Form Events: A readonly Embedded Field

4:46
27

Collection Filtering: The Easy Way

6:05
28

Criteria System: Champion Collection Filtering

5:24

> Symfony 3 > Doctrine Collections: ManyToMany, Forms & other Complex Relations

Buy Access to Course

17.

Join Entity App Refactoring

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $12.00

Previous Chapter

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or register to check out the script

10 Comments

Sort By

Login or Register to join the conversation

Mirko 7 years ago

Wouldn't it be better to have a composite primary key for the GenusScientist entity, consisting of two foreign keys (genus_id, user_id), since this way, with surrogate primary key (id), theoretically we can end up with the same two combinations of foreign keys (genus_id, user_id) under two different primary keys (id)?

|

MolloKhan SFCASTS Mirko 7 years ago

Hey @Mirko

That's a good point and it actually depends on your data constraints, if you have decided that you don't want to have duplicated combinations then you can set up unique constraints at the DB level. Check this out: https://www.doctrine-projec...

Cheers!

|

Mirko MolloKhan 7 years ago

Ok, so I can put a unique constraint on the genus_id-user_id combination if I want to. But, as I understand, GenusScientist table (entity) must not have the same combination of genus_id and user_id more than once, since this table acts like an intermediary table in many-to-many relationship between Genus and User.
My question is, if we make a combination of genus_id and user_id a primary key, then we don't need the surrogate id nor do we need to put a unique constraint on genus_id-user_id combination, since primary key is unique by default?

|

MolloKhan SFCASTS Mirko 7 years ago

Ohh, you have a good point and probably from a DB point of view that would be the way to go but to be honest I haven't done that on Doctrine, so, I'm not totally sure if it's supported or not (Maybe yes?). If you find more info about it please let me know :)

Cheers!

|

Mirko MolloKhan 7 years ago

Yes, I managed to do it with Doctrine by following this: https://www.doctrine-projec...
Down below are the annotations I used for the GenusScientist entity's primary key. For the remainder of the tutorial I just needed to do some minor adjustments, but otherwise everything went well.

/**
* @ORM\Id
* @ORM\GeneratedValue(strategy="NONE")
* @ORM\ManyToOne(targetEntity="Genus", inversedBy="genusScientist")
* @ORM\JoinColumn(nullable=false)
*/
private $genus;

/**
* @ORM\Id
* @ORM\GeneratedValue(strategy="NONE")
* @ORM\ManyToOne(targetEntity="User", inversedBy="studiedGenuses")
* @ORM\JoinColumn(nullable=false)
*/
private $user;

2 |

MolloKhan SFCASTS Mirko 7 years ago

Cool! Thanks for sharing it :)

|

Krzysztof K. 8 years ago

Do we have to keep field: id as a primary key for GenusScientist? What implictaions will be here if I will remove it and add composite primary key?

|

MolloKhan SFCASTS Krzysztof K. 8 years ago edited

Hey Krzysztof K.

Very interesting question! Honestly, I haven't had the need (or obligation) of using a composite primary key for my entities, but I found a nice article about how to do it: https://www.doctrine-projec...

I hope it helps. Cheers!

1 |

Krzysztof K. MolloKhan 8 years ago edited

MolloKhan thanks :) I will do some tests to see hoe it works, maybe I will comeback here with more questions.

|

MolloKhan SFCASTS Krzysztof K. 8 years ago

Excellent, I'm ready! (cracking knuckles)

|

This course is built on Symfony 3, but most of the concepts apply just fine to newer versions of Symfony.

Symfony 3

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.1.3",
        "symfony/symfony": "3.4.*", // v3.4.49
        "doctrine/orm": "^2.5", // 2.7.5
        "doctrine/doctrine-bundle": "^1.6", // 1.12.13
        "doctrine/doctrine-cache-bundle": "^1.2", // 1.4.0
        "symfony/swiftmailer-bundle": "^2.3", // v2.6.7
        "symfony/monolog-bundle": "^2.8", // v2.12.1
        "symfony/polyfill-apcu": "^1.0", // v1.23.0
        "sensio/distribution-bundle": "^5.0", // v5.0.25
        "sensio/framework-extra-bundle": "^3.0.2", // v3.0.29
        "incenteev/composer-parameter-handler": "^2.0", // v2.1.4
        "composer/package-versions-deprecated": "^1.11", // 1.11.99.4
        "knplabs/knp-markdown-bundle": "^1.4", // 1.9.0
        "doctrine/doctrine-migrations-bundle": "^1.1", // v1.3.2
        "stof/doctrine-extensions-bundle": "^1.2" // v1.3.0
    },
    "require-dev": {
        "sensio/generator-bundle": "^3.0", // v3.1.7
        "symfony/phpunit-bridge": "^3.0", // v3.4.47
        "nelmio/alice": "^2.1", // v2.3.6
        "doctrine/doctrine-fixtures-bundle": "^2.3" // v2.4.1
    }
}

Previous Chapter

Next Chapter