DoctrineBundle Updates & Recipe Upgrade

Hokey, I figured out that I could to this instead:

$analyses = $em->getRepository('App\Entity\Hazardlog\Analysis')->findAll();

Hey Matt,

Awesome, I'm happy you were able to figure it out yourself, well done!

Btw, you were very close in your 3rd try, i.e. the option with $analyses = $em->getRepository('Analysis::class')->findAll(); is almost correct, but it should be this way:

$analyses = $em->getRepository(\App\Entity\Hazardlog\Analysis::class)->findAll();
// or if you add the namespace as a use statement above your class - just:
$analyses = $em->getRepository(Analysis::class)->findAll();

I.e. It should not be in quotes ;)

Cheers!

Hey Mattias,

Good question! Well, it should look like "server_version: 'mariadb-10.3.35'", i.e. you should add that "mariadb-" prefix for MariaDB SQL servers - that's a standard you should just follow :)

But keep in mind that it's better to write there the version you have on production. And ideally, you should have the same version locally and on production so that it works without problems. Otherwise, you can try to specify the lowest version from both and see if it will work well. Otherwise, you would need to specify that version different for different environment using .env files.

I hope this helps!

Cheers!

Thank you! Yes, that was from the production server. But oh, I just realized that I have MariaDB in production, but for my local server I'm running <b>"Server version: 5.7.32 - MySQL Community Server (GPL)"</b> so they are completely different then I suppose.

So one way would be to put the respective versions in the DB connection strings.

I suppose another way would be to put a doctrine.yaml file in each of the config/packages/prod and config/packages/dev directories, and put this in the config/packages/dev/doctrine.yaml

doctrine:
    dbal:
        server_version: 'mysql-5.7.32'```

is that correct?

Hey Mattias,

Hm, well, they are not that much different fairly speaking.. but yeah, it's better to separate them. The more specific version you specify there - less problems you will have, and queries that Doctrine generates in migrations will be more optimized for too. But I used to have MariaDB on prod and MySQL locally and it works OK with the MariaDB server_version for me. So, it depends.

> I suppose another way would be to put a doctrine.yaml file in each of the config/packages/prod and config/packages/dev directories, and put this in the config/packages/dev/doctrine.yaml

Well, it might be enough for you, but it's not quite correct IMO, because you may load your project in prod mode locally... and what then? The website will use MariaDB version locally? If you never do this - probably it will be OK, at least this strategy is simple. But keep in mind that if you will generate a migration in dev mode - it will use MySQL version instead of MariaDB, but the problem that you want to use MariaDB as you need to run that migration on prod.

A better would be to create an env var in .env files and set it to MySQL version locally and to MariaDB version on prod- this should be the correct way to solve this.

But ideally, install and start using MariaDB locally too :)

> server_version: 'mysql-5.7.32'

Haha, uh oh, almost like that :) With MySQL it's simplified to just "5.7.32", you can see more config options here in the docs: https://symfony.com/doc/cur... . As you can see, MariaDB complicates that value a bit, but it's simple with MySQL. Actually, it's difficult to remember, so I usually look at the docs when I need to configure it.

Cheers!

Hey @elbarto

You can choose whatever naming strategy is convenient for you, or you can create your own strategy in case you need to. Check line 298 https://symfony.com/doc/current/bundles/DoctrineBundle/configuration.html

I believe the CamelCaseNamingStrategy is set by default, you can change it to use the UnderscoreNamingStrategy

I hope it helps. Cheers!

Hello Diego,

If i put back doctrine.orm.naming_strategy.underscore in my doctrine.yaml file, i then get a deprecation message : User Deprecated: Creating Doctrine\ORM\Mapping\UnderscoreNamingStrategy without making it number aware is deprecated and will be removed in Doctrine ORM 3.0.

The thing is, what solutions do we have if i want to pass from underscore to underscore_number_aware strategy and updating my database. Because as i said earlier, if i have few tables named table1_test , table2_test. They will become table_1_test and table_2_test.
On a schema:update it breaks because i have a bunch of relations (FK) inside of them, thus forbidding me to update my schema.

Thanks in advance !

Hmm, you can ignore that deprecation :D
or, another solution is to manually define the name of all the tables you have problems with

/**
 * @ORM\Table(name="table2_test")
 */
class SomeEntity

The naming strategy is only used when Doctrine have to give it a name to your tables/fields

Cheers!