…But what if we want to apply some criteria like this globally to every query to a table? Like, telling Doctrine that whenever we query for fortune cookies, we want to add a WHERE discontinued = false to that query. That sounds crazy. And yet…

…a constructor for this class... and open it up to give us some space. Now copy the Doctrine-related properties from ObjectTranslator's constructor ($translationClass and $doctrine) and paste them into our new constructor: This paves the way for our next method, public function idFor()…

…right now. This command also shows mapped superclasses, so we need to do some work to get our Translation class to show up here. You're probably used to using mapping attributes for your Doctrine entities. In bundles, it's a bit different. The official…

…run: symfony console doctrine:migrations:migrate Say y to confirm and... beautiful! It tells us that it's Migrating up to that specific version. It seems... like that worked! To make sure, you can try another bin/console command: symfony console doctrine:query:sql with…

…them. That's tragic! Instead, those messages were sent to the doctrine transport and are waiting patiently inside of a messenger_messages table. So... how can we read these back out and process them? We need something that can fetch each row one-by-one…

Let's keep track of the goal. When we first used stateOptions, it triggered the core Doctrine collection provider to be used. That's great... except that it returns User entities, meaning that those became the central objects for the UserApi endpoints. That causes a…

…too good to be true. It gives us all the flexibility, in theory, of a custom class, while reusing all the core Doctrine provider and processor logic. But hold your horses because there are two, albeit fixable, snags. Most importantly, we're not allowed to…

…text file. We're going to stop using this MixRepository and instead load these $mixes from the database. Ok: to save objects, we leveraged the EntityManagerInterface service, which is the most important service by far in Doctrine. Whelp, this service can also query for objects…

…gestion des utilisateurs, tests d'acceptation et tests unitaires. Mise en place de Doctrine avec PHPUnit, pour permettre un workflow TDD hautement productif. Tester ses classes Repository avec des opérations réelles sur les données tout en conservant une vitesse fulgurante. Tester ses Entity dans le…

Our UserAPI is now a fully functional API resource class! We've got our EntityToDtoStateProvider, which calls the core state provider from Doctrine, and that gives us all the good stuff, like querying, filtering, and pagination. Then, down here, we leverage the MicroMapper system to…

…back is a custom class. Well, technically you don't have to have a custom repository class - and if you don't, Doctrine will just give you an instance of EntityRepository. But in practice, I always have custom repository classes. Anyways, when we ask for…

…How can I insert a new row in the question table? We need to think: Let's create a Question object, populate it with data and then ask Doctrine to save it. To play with all of this, let's add a new, sort of…

…the database. But... that table does not exist yet. How can we create it? Well, because Doctrine has all of this configuration about the entity, like the fields and field types, it should - in theory - be able to create the table for us. And... it…

…goal: to move our code - which mostly lives in config/ - into the new directory structure. The next section is doctrine... and there's nothing special here: this is the default config from Symfony 3. Compare this with config/packages/doctrine.yaml. If you look closely…

…users, we need to be able to run some code after API Platform deserializes the JSON into a User object, but before it gets saved to Doctrine. That code will encode the plainPassword and set it on the password property. How can we do that…

We need to talk about a very, very important and, honestly, super-confusing part of Doctrine relations! Listen closely: this is the ugliest thing we need to talk about. So, let's get through it, put a big beautiful check mark next to it, then…

…to have many Comments... and we want each Comment to belong to one Article. Forget about Doctrine for a minute: let's think about how this should look in the database. Because each Comment should belong to one article, this means that the comment table…

Hey friends! I mean, hello fellow space-traveling developer... friends. Welcome, to part two of our Doctrine tutorial where we talk all about... relationships. Oh, I love relationships, and there are so many beautiful types in the universe! Like, the relationship between two old friends…

Let's see what this all looks like in the database! To query the user table, we can actually use the console: php bin/console doctrine:query:sql 'SELECT * FROM user' Nice! We inherited a bunch of columns from the base User class, like username…

…do! I mean, a query isn't truly interesting unless you're joining across tables to do some query Kung fu. Doctrine makes JOINs really easy - it's one of my favorite features! Heck, they're so easy that I think it confuses people. Let…