ManyToMany & Fixtures

Hey Vince!

Hmm, a few things. First, when you query for an entity (e.g. a list of ProductCategory objects), Doctrine *only* fetches the data for the ProductCategory objects - it does not automatically go and fetch the related data (of course, you can change your query with a JOIN to explicitly tell it to select the extra data, but it doesn't happen automatically). However, as soon as you reference the related data (e.g. $productCategory->getProducts()), Doctrine queries for that data then. In other words, Doctrine only queries for data that you're actually using.

But, how are you turning your object into JSON? Are you using Symfony's serializer, or the JMS Serializer? If so, both, by default, serialize *all* properties. In other words, even though you only queried for (for example) one ProductCategory (and Doctrine *only* fetched its data), when you serialize this to JSON, the serializer activates all the related properties causing everything to be lazy-loaded to create the gigantic JSON. Obviously, that's not cool :). To fix that, just choose *which* properties you do and don't want to serialize. With JMS Serializer, use @ExclusionPolicy and @Expose. With Symfony's serializer, use the serialization @Group annotation.

Let me know if this helps! Cheers!

Ow yeah. I forgot to mention serializer. Anyways, Thanks for the helpful info

Yo James!

Hmm, I'm not sure - I'm a little surprised that it doesn't work. The only issue I can find on it is this: https://github.com/nelmio/a... - which makes it sound like it should work. What does your code look like and what error do you receive?

Cheers!

I think I figured it out, and I need a middle table so one to many as my related products need to be assigned to a certain position.
I have another table which actually is staying as a many to many table which is in between products and categories. Many product can be found in many categories and the inverse. I followed the whole process to add a many to many relationship but when loading fixtures I encounter this error:

[Doctrine\ORM\ORMInvalidArgumentException]
Expected value of type "Doctrine\Common\Collections\Collection|array" for a
ssociation field "AppBundle\Entity\Category#$categoryProducts", got "AppBun
dle\Entity\Product" instead.

Do you see what is the problem?

Thanks

Hey Connect,

I suppose you're trying to set a single Product entity, *but* your setCategoryProducts() method expects an array, i.e. ArrayCollection. Do you have an adder method, i.e. addCategoryProduct(Product $product) ? We have a nice note about our addGenusScientist() method in this article which says:
<blockquotes>
> Hey! I see an addGenusScientist() method! I'll just call that twice instead of looking for a setter
</blockquotes>

Please, double check you have the similar adder method in your entity.

Cheers!

I think it is all done good on my entity file:

/**
* @ORM\ManyToMany(targetEntity="Category", inversedBy="categories")
* @ORM\JoinTable(name="category_product")
*/
private $categoryProducts;

public function __construct()
{
$this->categoryProducts = new ArrayCollection();
}

then

public function addCategoryProduct(Product $product)
{
if ($this->categoryProducts->contains($product)) {
return;
}

$this->categoryProducts[] = $product;
}

/**
* @return ArrayCollection|Product[]
*/
public function getCategoryProducts()
{
return $this->categoryProducts;
}

I can't see an error :/

Sorry stupid mistake from my side with * @ORM\ManyToMany(targetEntity="Category", inversedBy="categories") at the place of * @ORM\ManyToMany(targetEntity="Product", inversedBy="categories")

Oh, I see. Good catch!

Btw, I use "$ bin/console doctrine:schema:validate" to validate mapping - it helps a lot.

Cheers!

Hey Mohammad,

Could you show a signature of your setGenusScientists() method? Actually, we don't have this method in this screencast, but we have "public function addGenusScientist(User $user)" instead. I believe this should work: "genusScientists: '3x @user.aquanaut_*'" - see the last code block in this screencast, but it's a bit weird that you have setter for collection, which requires a single User. Adder fits much better here.

Cheers!

Hey Xi Wang!

I haven't done this before - and it depends on your setup - but you'll probably want to use a custom processor: https://github.com/hauteloo.... Basically, when a specific entity is being saved, the processor is called. Here you can handle your logic - e.g. copy some fixture file into an uploads/ directory and set the filename on the entity. Or, upload a file to S3 and set its filename on the entity.

Let me know if that works out well for you!

Cheers!

Yo Ryan! weaverryan

Thanks heaps! I totally forgot about this 'hook' although I saw it somewhere here loooong time ago! And you're awesome as always! :)

Now, when making decisions on using those extra layer bundles - how do we weigh the pros and cons in a project management point of view? I mean do we really need hauntlook/AliceBundle on top of theofidry/AliceDataFixtures and then in the dark deep core it is just nelmio/alice and faker?

I can do it the old fashion way as below, and I'm really curious about the trade-offs other than few console commands or config options (and some of these are really poorly documented through out the versions and quite difficult to keep up with).

Cheers!

class LoadFixtures implements FixtureInterface
{
    public function load(ObjectManager $manager)
    {
        $uploadDir = __DIR__ . '/../../../web/uploads';
        $fileUploader = new FileUploader($uploadDir);

        $processors[] = new ImageFileProcessor($fileUploader);

        Fixtures::load(
            __DIR__ . '/fixtures.yml',
            $manager,
            [
                'providers' => [$this]
            ],
            $processors
        );
    }

Hey Xi Wang!

Great question :). Honestly... over the past few years, AliceBundle has gotten more complex, and now there are a bunch of dependencies. I know the author - he's got a good idea in mind... but for me, *just* to be able to load fixtures, I really don't like the new complexity. So going forward, *if* I use Alice, I'm still using it in this simpler way (like you posted). More long term, I *may* stop using Alice entirely... but I think we (in Symfony) should make a few improvements to the DoctrineFixturesBundle to make a few things easier. What's *really* great about Alice is how easy it is to (A) add a bunch of items in a loop, (B) reference items together and (C) use Faker. This can all be done in DoctrineFixturesBundle, but it's much less elegant. I hope we can make it more elegant in the future.

tl;dr is this: I like using Alice in the more manual, but simpler way that you described. But if you run into too many issues, I'd recommend using DoctrineFixturesBundle manually.

Cheers!

Hey Peter,

Most of the time, it's just enough `@tags_*`, but yeah, sometimes it could be useful!

Cheers!