Doctrine & the Database in Symfony 4

Hey Paweł C.!

Fascinating question! Let me answer with various points:

1) Does it make sense for you to map each table to a database class?

Maybe. In some projects, it's quite common to be consistent working with the data for one table. Like, "Hey! Give me the data from the product" table. But, in other projects - especially if you have a complex or legacy database - you are more commonly grabbing data from many different tables and using them all at once. In that context, it's probably not that helpful.

2) How to organize Symfony project without ORM (Doctrine) to keep controllers clean and slim?

In general, the important thing is this: create "model" classes (by this I mean a class that holds data like a Doctrine entity, but is just a normal PHP class) that are meaningful to your "business logic". If this matches your database table structure (e.g. a "product" is a meaningful concept in my code and I also have a "product" table), great! If it does not match your table structure, no big deal. Here's a nice way to think about it: if you aren't modeling your database to PHP classes currently, then you are probably passing around a lot of associative arrays of data. For your application, those arrays are meaningful. And if you are commonly passing around an array with more or less the same data in it, this is probably an "important concept" in your app, and you could convert it into a class. For example, suppose you query 5 database tables at once to retrieve a bunch of "product shipping information". Cool! It might be helpful to create a ProductShippingInfo class and put the data onto that class instead. Then, instead of passing that array around, you are now passing a class around.

So, my general advice is this:

A) Find patterns of data that you fetch from the database. And, if it's helpful, start returning those things as objects. And, the same is true in the other direction: if accept 20 parameters from a form, consider creating a class and putting that data into a new instance of the class. And then passing it around to your system.

B) And apart from creating "model" classes, create a rich service layer. Basically, each time you need to "do" something, put that code into a service class. I also (outside of Doctrine) still follow the Doctrine "repository" method where I have a class that holds all of the queries for each table (so 10 tables == 10 repository classes). This is easy to do even outside of Doctrine. Though, again, if your more commonly querying from 5 tables, then maybe you follow this idea, but it doesn't really match your database structure.

So, here is a "pretend" before and after. Before:

$name = $request->request->get('product_name');
$price = $request->request->get('price');
// 10 other fields

$pdo->query('INSERT INTO ...'); // then you build the query to pass these 10 things

After:

$name = $request->request->get('product_name');
$price = $request->request->get('price');
// .. 10 other fields

$product = new Product($name, $price, ...);

// this service class has a nicely-named method and receives a Product class
// it would take care of the ugly query inside
$productManager->createNewProduct($product;

It's not a science, and there are people that are much better at this than I am. But, generally, turn "data" into classes & objects. And put all of your "work" into service classes.

I hope this helps!

Cheers!

Damn good and exhausting answer. Thank You!

Hey Sławomir G.!

GREAT question. I was having that same thought after writing it this way :). If I were to recreate this function to be more flexible, I would probably just force the user to do this step. So, it would look more like this:

$this->createMany(10, function($i) {
    $article = new Article();
    // ...

    return $article;
});

Then, the createMany() function would look at the class of the object that was returned to know how to store it as a reference :). I think this is just as easy, but more flexible.

Cheers!

Hey Lavin

How are you handlig that route? (/product )
It looks like you are creating and saving a new product by only accessing to that route

Cheers!

thank for answer finally found it xD but thank for answering :)

can i ask another question?

in this chapter https://symfony.com/doc/2.8...
part updating the object i create the code like this

/**
* @Route("/product/edit/{productId}")
*/
public function updateAction($productId)
{
$entityManager = $this->getDoctrine()->getManager();
$product = $entityManager->getRepository(Product::class)->find($productId);

if (!$product) {
throw $this->createNotFoundException(
'No product found for id '.$productId
);
}

$product->setName('New product name!');
$entityManager->flush();

return $this->redirectToRoute('product_show', [
'id' => $productId->getId()
]);

//return $this->redirect($this->generateUrl('product_show', array(
// 'product' => $product,
//)));
}

but i got the output like this Call to a member function getId() on string

what should i do to fix it so i can get proper output thank you

Oh, that's because you are calling "getId()" on $productId variable instead of $product

Hey Tomasz N.!

So... this is likely a bug in the MsSQL driver inside Doctrine. I don't know for sure, but I had a Doctrine guy look at this, and, at first glance, what you're trying to do seems reasonable and we don't see any problems. It's probable that when you run doctrine:schema:update, it's looking at the wrong "schema", seeing 0 tables, and so, then doing a CREATE TABLE. The only work around I know of is basically to fix this "by hand". I would use the migrations system (so, run make:migration), then manually modify the migration file to change it to the ALTER TABLE that's needed.

Sorry I can't be of more help! The MsSQL driver doesn't get as much attention as the others.

Cheers!

Thanks Ryan. I suspected, it's doctrine malfunction. I will do like you say, maybe someday doctrine guys will correct this.

Hey Pawel,

We're sorry for this spam! Our Disqus account receiving many spam messages lately :/ But good news is that most of them are recognized by Disqus as spam automatically.

Cheers!

Yo Mohamed K.!

Wow! That's a new error for me! Oh boy, it looks like MySQL 8.0.4 my have changed the default way that you send your password to them :/. Here is some info on how people are fixing / working around this:

* https://github.com/laradock...
* https://stackoverflow.com/q...

Also, this was apparently fixed in PHP 7.2.4 - you can read a bit about that here: http://php.net/manual/en/re...

Hopefully one of these will give you an easy fix! It's too early in this tutorial to hit a big snag - you haven't had any fun yet!

Cheers!

Hey Jimmy S.!

Ah, so happy to hear it! If you have any questions, thoughts or suggestions, definitely let us know down in the comments (or shoot us an email).

Cheers!

Hey odds

Haha, you "may" be lazy but it's our fault as well. For some reason it wasn't added to the track, but I just did it!
Thanks for reporting it :)

Have a nice day

Hey Prout,

Yes, we have the one but in Symfony 3 track. This course was recorded in a Symfony 4 way using Flex and our new "The Spacebar" Symfony 4 project.

Cheers!

Hey Nizar!

You can read about all of that here: https://symfony.com/doc/current/doctrine/multiple_entity_managers.html. The configuration in that article will need to be a bit different to support environment variables, but hopefully it will get you started. For autowiring all the entity managers, I would use a bind rule (https://knpuniversity.com/screencast/symfony-fundamentals/services-config-bind) to bind to argument names - like $adminEntityManager if you had an em called "admin".

Cheers!

Hey Mauro!

Yea, these commands are still being updated to work with Symfony 4. The big issue is actually pretty simple: you don't have a bundle in Symfony 4 :). Here are some more details: https://github.com/doctrine....

So, as you can see there, right now, there are some workarounds, like temporarily creating a bundle. But pretty soon, I hope it will be updated to work without a bundle.

Cheers!

Hey Peter K.!

This is next in the Symfony series - and I want to get it out soon. But, it will be at least several weeks, for two reasons. First, we'll release the Webpack Encore & React tutorials first. And second, there's a pull request on MakerBundle that we really *need* for this tutorial. So, it needs to be merged and released still. But I'll try to get it all done as quickly as possible :).

Cheers!