The 4 (2?) Possible Relation Types

Hey boykodev!

Try making that column length a little shorter - like length=180. The problem is InnoDB + using the utf8mb4 encoding. It ultimately tries to make a key length that is longer than is supported. If you're able to shorten the field length, it also makes the key a bit shorter.

Here is a discussion about that, from FOSUserBundleL https://github.com/FriendsO...

I'm a little surprised I didn't have that issue during this tutorial - I have seen it in other places.

Cheers!

Thanks for this hint. I ran into the same problem. Shortening the length to 180 worked for me. I edited the VersionXXXXX.php file within the Migrations folder and executed the php bin/console doctrine:migrations:migrate afterwards without errors.

this solution works fine

That problem occurs when you are on MySql 5.6 and using "utf8mb4" charset, if you upgrade to MySql 5.7 then you won't have that problem again.

Cheers!

Hey David B.!

I couldn't agree more - I've always thought Doctrine fixtures were clunky - and it's been on my list for a long time to improve it. But, that's *also* why we added our own mini-fixture system on top of Doctrine in this tutorial. I think we finish/user that system in this video - https://symfonycasts.com/sc... - you can see how you can create a collection of (for example) Article objects by using fake data inside a callback. You don't return an array like an Eloquent factory, but that's due to the way Doctrine is built - you tend to deal more directly with your objects vs returning arrays and having Eloquent magically put those onto your objects (it does look good though in the factory)!

Does the system we create in this tutorial somewhat address what you're thinking? I'd love to know!

Cheers!

Thanks for your answer weaverryan ! I'm not sure that Fixtures are completely clear for me to use it without any problems, but I hope they will. The main misunderstanding point for me is generic types while getting a reference to relation, saving references and their naming.
I think we should pass it ($className . '_') to it's own method which will return the reference prefix. This also could change in the future. BTW, we don't need to pass the $entityManager as an argument and to the callback because we an use $this->manager, am I right?

Hey David B.!

Sorry for my slow reply!

I think we should pass it ($className . '_') to it's own method which will return the reference prefix. This also could change in the future.

I didn't quite understand what you mean by this part. Could you tell me more? If you fully create the BaseFixture class like we do on that tutorial, you should never need to worry about setting references (it's done in the background for you when you use the $this->createMany() method) and you can use $this->getRandomReference() to fetch a random reference. But if you find ways to improve the data for your own use, please do :).

BTW, we don't need to pass the $entityManager as an argument and to the callback because we an use $this->manager, am I right?

Correct! They are exactly the same object - so you can use either. Using $this->manager is just easier in this case (because you don't need to pass anything to the callback directly).

Cheers!

Hey Student,

This error looks like you have namespace problems. Please, open "src\DataFixtures\TagsFixtures.php" file and make sure it has a proper namespace i.e. "App\DataFixtures\TagsFixtures".

Cheers!