Clase de entidad

Hey Michail!

GREAT question. That was a design decision in MakerBundle and the goal was to be "friendly" over "strict" (definitely a subjective decision). So, if make bundle instead generate things like private string $title, then if the user called $obj->getTitle() before setting it, they would get the "not initialized" error from PHP. So, to make the entities behave identically to the "pre property types world", we made them nullable and default to null. It's very possible that, as a community, we will eventually desire to be more strict... or we might even add an option in MakerBundle. But, that's the explanation :).

Cheers!

Hey @RafaelBraga

That's interesting. Perhaps it's due to your PHP or Symfony version. What versions do you have? Try upgrading them

Cheers!

Hi @MolloKhan

I'm using PHP 8.2.10 and Symfony 6.1.12. I will upgrade Symfony and try again.

Thank you!

Ok, typed properties are a feature of PHP 7.4, so that's not the problem. It could be related to your Symfony/MakerBundle version. Let me know if it works after upgrading

Cheers!

Hey Patrick,

If you made a typo - you need to do Ctrl + C (or Cmd + C on a Mac) to exit the command and re-run it again :) It might be so that command already wrote some code to your files, so you need to revert those changes and remove created fields if they contain your mistake and you don't want to fix it manually in those files. That's why it's a good idea to commit all the changes before running make commands, as you can easily revert uncommit changes with git.

Cheers!

Yeah I religiously use git and did the same thing actually. I was just wondering if what I'm doing is too hacky and if there's a "Symfony Way" of doing it. Thanks for confirming! Cheers~

Hey BYT,

We always use PHP attributes (or annotations on old tutorials) for configuring entities, so I can't point you to any tutorial but you can see examples in the Symfony docs. For example, you can see how to configure an association here (just click on the YAML option) https://symfony.com/doc/current/doctrine/associations.html#mapping-the-manytoone-relationship
And you may want to read how to configure your entities when using YAML https://symfony.com/doc/current/reference/configuration/doctrine.html#custom-mapping-entities-in-a-bundle

Cheers!

Hey BYT,

I don't think so... unless you will find a bundle or a library on GitHub that may help you with this. Doctrine only allows you to import mapping information from an existing database - for this you can leverage doctrine:mapping:import command.

If it's not something you need - I think you can create your own Symfony command and read the CSV file to import all the data from that, i.e. create entity files based on the schema in that file.

Cheers!

Hi

I want to be sure that I understand this right. I want to start new project, and I already have the database, with about 200 tables in it.

If I run "symfony console doctrine:mapping:import" command, an entity for each table will be created for me? Is my assumption correct?

Thanks.

Hey @t5810 ,

Yes, that's how it suppose to be used, it creates entities with the corresponding mapping. But on practice, it depends on how well you have your legacy DB configured. But you can easily try it and see how it works for you ;)

Cheers!

Hey Dmitriy,

But Doctrine already does this for you. You just need to generate an entity via MakerBundle, or make sure your User entity has this mapping config:

User
{
    #[ORM\Id, ORM\Column, ORM\GeneratedValue]
    private ?int $id = null;
}

Every time you will create a new entity - it will generate a sequential and inextricable ID for it. But if you delete a user from the DB - it won't be sequential anymore I suppose, and nothing much you can do with it.

I hope this helps!

Cheers!

Hey Wei,

Unfortunately, no. The Maker bundle follows Symfony's best practice when all your entities are in the src/Entity/ folder. This is also done for the simplicity of this command. The easiest way would be to generate an entity in that folder and then move it to another folder if needed.

Well, technically, you can put your entity in a subfolder of the src/Entity/ with the following syntax:

bin/console make:entity Subfolder\\YourEntityName

But if you're looking for a way to create it outside of the default src/Entity/ - nope, you would need to move it manually there.

I hope this helps!

Cheers!