Fetching Data & The Repository

Hey Sherri,

Thank you for sharing your knowledge with others :)

Cheers!

Hey Ngan-Cat,

It depends if you have Symfony Plugin installed or no. In this tutorial Ryan has it installed and enabled, that's why he get that autocomplete. You can take a look at this video to know how to install and enable it: https://symfonycasts.com/screencast/phpstorm/setup#plugins

Otherwise, you can hint your IDE about what class is that object by using @var annotation above the var, e.g.:

/** @var \App\Repository\QuestionRepository $repository */
$repository = $entityManager->getRepository(Question::class);
$repository-> // now you should have autocomplete here :)

I hope this helps!

Cheers!

How to know which library should I use? Like you used your "\App\Repository\QuestionRepository $repository" seems like out of nowhere..

Hey fUb,

Well, it depends on what repository you need. If you call "getRepository(Question::class)", then I know that the repository behind of that Question entity is QuestionRepository. If you're not sure - you can try to dump the $repository var, e.g. with "dd($repository)" - it will give you a hint about instance of what class is that var.

Cheers!

Hey Oliver-W!

A very warm happy new year to you too - and I echo your sentiments ❤️.

Hmm. What method are you using to execute these 2 queries? This isn't something I've done before, but I'm sure it's "allowed", but it's possible that you need to use the DBAL directly (i.e. a lower level) to allow this.

Cheers!

Hey Ryan,
I am using

        $repositorycust = $em->getRepository(Timeperiods::class);
        $conn = $em->getConnection();
        $query = "UPDATE `timeperiods` SET `cleared`=\"$renr $filename.PDF\" WHERE `id`=" . intval($datum["id"]);
        $stmt  = $conn->prepare($query);
        $stmt->execute();

To make it work, I execute the query for every set of data. Before I concatenated the statements and made one query.

Cheers!

Hey Oliver-W!

Hmm. That's what I would have used too. I'm not sure why concatenating doesn't work. This looks technically possible, though "iffy" - like it's not something that you're really "supposed" to do. So, I would keep your solution of executing 1 query at a time.

Cheers!

Hey Ryan,

or I could use ...where id=1 OR id=2 and so on.

Sometimes live is really hard! Thx for your time and help

Oliver

Hey Ali_M!

A very happy new year to you too :). Now, let's see about your question!

The error I get is: Class 'App\Entity'.$ffn.' does not exist.

Ok, I'm going to assume that the $ffn variable is set to the "short" class name of your entity - like the string Product. If that's the case, the code you need is:

$entities[] = $this->em->getRepository('App\Entity\'.$ffn)->findBy(['isActive' => true);

That should do it :). The ::class thing is something that you can call on a class to turn it into the full class name of that class. For example:

use App\Entity\Product;

echo Product::class;
// prints the string "App\Entity\Product"

So, ::class is just a convenience thing when you have a use statement. But it's not required. For example, just using the full string is identical:

use App\Entity\Product;

dump(Product::class === 'App\Entity\Product');

So, you've basically got it right - there's just not need to add the ::class. Actually, the fact that 'App\Entity\Continent'::class works surprised me - but I guess PHP is super friendly. And so, in theory, your other solution may have worked with some tweak, but the ::class simply isn't needed.

I hope this helps! Also, OCP is great, but, if you want some advice that you didn't ask for, be careful not to over-complicate things too early in a project ;). I typically put things into the database and make them dynamic only if I (or an admin) need the ability to change those values at runtime via an admin interface. For something like Language , it depends on the purpose of your app, but in many cases, if I want to add a Language, if that required a code change, I'd be ok with that.

Cheers!

Cheers!

Wonderful... It works just fine now, thanks to you... though I had my 20-minutes of head-scratching trying to get it to work. It was the backslash scaping effect during concatenation causing issues.. I invite you to look at my attempts leading to victory :)
`$c = "Continent"; //refers to an Entity class name

    dump(Continent::class === 'App\Entity\Continent'); // true
    dump(Continent::class === 'App\Entity\'.$c); // false, syntax error for unclosed parantesis.');//now it's closed!
    dump(Continent::class === 'App\Entity\'.$c.'); // false.
    dump(Continent::class === "App\Entity\".$c); // false. Unclosed '(' on line blahblah");// now it's closed
    dd(Continent::class === "App\Entity\\".$c); // true :)`

As to your valuable advices, you are correct. I do want to create an admin dashboard allowing to turn some of the form fields on & off. So that's why I considered adding them to the DB.
And that "Language" thing, it's not related to translation or locale or things like that. It's just another entity just like Continent, Country, etc. A mere list.
I am aware and actually used the Symfony form type country , however, in this project I need 100% control over my code and to allow the admin to tweak the form render to the fullest. i.e. Should the form show the Country field? Which countries should be hidden in the list? All of these to be controlled by an admin.
As to the OCP, It's in my todo list to watch your tutorial on SOLID soon enough ;)
Appreciate your help.

Hey Ali_M!

Nice job experimenting! Yes, the backslash makes perfect sense - that's an annoying character sometimes :). Good luck on the project - it sounds cool!

Cheers!

Hey Tomas,

Good qustion! Well, ManagerRegistry is something more global in Doctrine, it will allow you to get instance to the entity manager iteself, to other Doctrine features. You can look at that service to see what you can do / get with it. With the EntityManagerInterface you only get the part of Doctrine features, i.e. the actual entity manager only. So, if you don't need the whole Doctrine features and only need the entity manager to be able to persist() and flush() data for exmaple - better to inject EntityManagerInterface, as it
s more precise dependency. If you even don't need those persit() and flush() methods - perfect, you probably even don't need an entity manager at all. Maybe you just need an entity repository? Inject the repo you need, e.g. UserRepository in case you need to get access to User entity data. The more specific services you inject - the better. So, it really depends on your specific case.

About ObjectManager - that's too low-level thing usually, mostly used in case to make unit tests easier to set up because it's easier to mock up it.

In short, depending on what you really need to get in your methods - inject the specific services that give you specific features you need, don't need to inject the global objects that gives you literally everything while you're using only a tiny part of it. This will help you when you will be testing your code as well, it would be easier to mock up :)

I hope it clarifies thing for you a bit!

Cheers!

Hey m3tal

You can pass a DateTime object as a parameter if the field is configured as a Datime or Date. In your case it may be better to write a custom query instead of using the generic `findBy()` method

Cheers!

Hi MolloKhan,
thanks for taking your time.
Finally I have opted for this road of creating a custom building because find method doesnt satisfy my needs.
thank you very much.

Hey there,

It seems to me you forgot to define that environment variable, just add it to your .env or .env.local file

Cheers!