Saving Relations

Hey Houssem!

Are you referring to database transactions? If so, excellent question!

First, Doctrine automatically wraps its operations in a transaction. You can actually see this in one of our videos - https://symfonycasts.com/sc... - just hit "play" and you'll see how Doctrine has wrapped the INSERT query in a transaction. So if you're inserting 2 related objects at once, and one fails, both will be rolled back. You don't even need to think about it.

But, you *can* manually start and commit a transaction if you want. That's useful if, for example, you need to save something to the database AND send some data to an external API... and if the API call fails, you want to "roll back" your database query. We don't have any videos on this, but it's fairly straightforward: https://www.doctrine-projec...

Let me know if that helps!

Cheers!

Hey Mastou,

Why persist($comment)? Because we just created that Comment object. So, basically, if you create a new entity, to say Doctrine to store that object into DB you need to call persist on that object first, otherwise that object just won't be stored in the DB, Doctrine will just ignore them. So, the strategy is the next: create a new entity object, fill in some data on it, them call persist() on it to say Doctrine to save this object on next flush() call, and actually call flush() so doctrine execute queries and save everything that was modified into the DB.

To know more about that "use($manager)" syntax - google anonymous PHP functions, or just see this link to PHP docs: https://www.php.net/manual/... . Basically, it helps to pass some context to that anonymous function, i.e. in our case we allow to use that $manager object *inside* that function.

I hope this is clearer for you now!

Cheers!

Hey brentmtc,

First of all, you can check if your mapping is correct with "bin/console doctrine:schema:validate" command. Suppose, it is correct, then it should just work. You just need to persist both entities, i.e. call "->persist($user)" and "->persist($userAccount)" and only then call one "->flush()" that will save both entities to the DB.

If you still have this problem, hm, then what exactly id is null in the error? UserAccount::id or UserAccount::userId? Please, check your id property declaration, does it looks like this in both User and UserAccount entities?

/**
 * @var integer
 *
 * @ORM\Column(name="id", type="integer")
 * @ORM\Id
 * @ORM\GeneratedValue(strategy="AUTO")
 */
private $id;

Cheers!

Thank you. I was able to get this working by adding a user_id field to my user_account table.

Hey again Yaroslav Y.!

Can you explain a bit more? Do you just mean that it's a bit inconsistent to use Faker for many of the properties, but use hardcoded text for the article content field? If so, you're right - but it was also done on purpose - we include some markdown formatting in that string, so we can see that markdown processing is working, and also include a few words that we check for later for a feature. Basically, we wanted to control the article content... but the downside is that (you're right) it's not random anymore.

Cheers!

Hey Symfonybeard ,

I suppose you're on Windows OS. Try to use double quotes instead, i.e.:

php bin/console doctrine:query:sql "SELECT * FROM comment"

Does it help? :)

Cheers!

Great, this works! Thanks for your help. :)))

Glad it works! Yeah, a tricky thing about Windows console I learned from other users :)

Cheers!

Ha! Perfect! That's why we do it... but it's nice to have feedback that it's working! Keep going!!!! :D

Cheers!

Hey fahani!

Yep! It's nothing to worry about. There is some deprecation things happening right now... which should go away when doctrine/orm releases their next version. You can happily ignore this ;).

Cheers!

Hey toporovvv ,

You're totally right! Thanks for letting us know. Probably not a big deal, we've kept it so you can easily modify our example and see that there's an extra $count argument which you can use if you need.

Cheers!

Hey GDIBass

If you have to use a local variable inside a callback function, then you have to specify it by doing what you did. The compiler requires to keep track of the reference of that variable some how :)

Cheers!

Yup. I didn't see another way of adding comments referencing the article while also having $manager to persist.

I know it's not obvious yet, because (at this moment) the video & code blocks aren't released yet, but yes, we do this exact thing - the script contains:

At the top, use the $manager variable

So, you're doing it totally right :). Later, we'll cleanup things a bit and put Comments into their own fixture class. But for right now, that use is needed to get the $manager variable in scope so we can persist the comments.

Cheres!