Chapters

23 Chapters | 2:22:24 |

01

Installing Doctrine

7:54
02

make:docker:database

5:24
03

docker-compose & Exposed Ports

4:46
04

docker-compose Env Vars & Symfony

4:59
05

doctrine:database:create & server_version

4:49
06

Entity Class

7:57
07

Migrations

5:34
08

Persisting to the Database

8:42
09

Fetching Data & The Repository

5:28
10

Entity objects in Twig

4:55
11

"5 Minutes Ago" Strings

3:15
12

Custom Repository Class

8:10
13

DQL & The Query Builder

6:49
14

Reusing Query Logic & Param Converters

3:35
15

Automatic Controller Queries: Param Converter

3:28
16

Smarter Entity Methods

7:57
17

Request Object & POST Data

8:08
18

Update Query & Rich vs Anemic Models

7:58
19

Data Fixtures

5:18
20

Foundry: Fixture Model Factories

5:56
21

Foundry Tricks

7:28
22

Sluggable: Doctrine Extensions

5:57
23

Timestampable & Failed Migrations

8:01

> Symfony 5 > Doctrine, Symfony & the Database

Buy Access to Course

10.

Entity objects in Twig

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $12.00

Previous Chapter

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or register to check out the script

14 Comments

Sort By

Login or Register to join the conversation

davidmintz 4 years ago edited

noob question about docker. I set up the database service with mariadb, yadda yadda, turned off the machine, turned it back on today and was quite surprised that the question table we created in the migrations chapter was still there, even though my docker-compose.yaml doesn't say anything about volumes. so let's see -- the state of the database persists in the docker image after you shut down the container? so, you only lose your db data if you <i>destroy</i> the image? If so, that seems reasonable enough!

|

weaverryan SFCASTS davidmintz 4 years ago edited

Hey davidmintz!

Yup, I think you basically got it! Well, let me clarify one point. When you "turn off" a container, you can do one of two different things:

A) docker-compose stop. This turns off the containers, but does not delete them. It's like turning off your computer.
B) docker-compose down. This turns off the containers and removes them. It's like turning off your computer then destroying the hard drive.

So, I believe that it's less about "destroying the image" and more about "destroying the container" (which was built from the image). A minor detail, but for understanding things, it might help :). To further the distinction, you could have multiple containers that are all built from the same image, but they each of their own, separate data (e.g. the hard drive of each was built FROM the image, but is now its own, standalone machine).

Cheers!

1 |

davidmintz weaverryan 4 years ago edited

Gee, I thought I was getting it but now I really <i>am</i> confused! (-: I'm kidding -- sort of. I do docker-compose down but it doesn't seem to destroy the "hard drive", i.e., the data in the database. I get the sense that where the docker docs say "remove" in this context, they mean remove from memory, not delete from disk. True?

And it feels as though stop is rather like hitting pause... no wait. I see docker also has its pause command. Never mind -- I'll get it all straight at some future date.

|

Ibrahim E. 5 years ago

Could not show question name and question on the page, instead getting this error "Object of class App\Entity\Question could not be converted to string
"

|

Ibrahim E. Ibrahim E. 5 years ago

I managed to solve the issue by overriding the __toString method in Question class.

|

Victor SFCASTS Ibrahim E. 5 years ago

Hey Ibrahim,

Well done! Yes, that error means that you need to add a __toString() magic method to teach the PHP how to convert your object into a string, or call the method explicitly in a place where you're trying to "print" the object.

Cheers!

|

Farshad 5 years ago

Weird thing is. I dont get autocomplete and question.name doesnt work. But question.getName() does work!
Is that okay? Or is it weird?

|

MolloKhan SFCASTS Farshad 5 years ago

Hey Farry7

It's not strange, it happens to me from time to time. Symfony plugin is not perfect, I usually trigger a "clear index" (inside PHPStorm settings) action and it solves the problem

Cheers!

|

Gediminas N. 5 years ago

At 0:55 in my IDE it doesn't autocomplete the records, is there some way to make my PHPStorm like yours?

|

sadikoff Gediminas N. 5 years ago edited

Hey Gediminas N.

Do you have Symfony plugin installed and enabled in your PHPStorm?

Cheers!

|

Gediminas N. sadikoff 5 years ago edited

Hey sadikoff ,

Yes

|

sadikoff Gediminas N. 5 years ago edited

Wow that's weird. Try to check plugin configuration, fix path inside it. There is old default config, which needs to be adjusted after plugin enabling. On main plugin settings you should check app and web directories they should point to src/ and public/ also translation paths should be adjusted. Also it's good to check Twig, Container and Routing tabs. The best way to get everything work here is to press reset to default button

Cheers! I hope this will help!

|

Steven 5 years ago

Hi,

2:53 little html issue.
By adding parse_markdown filter, the question goes out of p.d-inline tag :/
New paragraphs are generated by markdown.

Cheers!

|

weaverryan SFCASTS Steven 5 years ago edited

Hey Steven!

Haha, yea, you're 100% right :). I noticed this when I was editing the video... but too late then. So yea, in reality, the p tag around the processed markdown should probably be a div, otherwise you get p tags inside of p tags.

Cheers!

1 |

This tutorial also works great for Symfony 6!

Symfony 5 Doctrine 2

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.4.1",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/doctrine-bundle": "^2.1", // 2.1.1
        "doctrine/doctrine-migrations-bundle": "^3.0", // 3.0.2
        "doctrine/orm": "^2.7", // 2.8.2
        "knplabs/knp-markdown-bundle": "^1.8", // 1.9.0
        "knplabs/knp-time-bundle": "^1.11", // v1.16.0
        "sensio/framework-extra-bundle": "^6.0", // v6.2.1
        "sentry/sentry-symfony": "^4.0", // 4.0.3
        "stof/doctrine-extensions-bundle": "^1.4", // v1.5.0
        "symfony/asset": "5.1.*", // v5.1.2
        "symfony/console": "5.1.*", // v5.1.2
        "symfony/dotenv": "5.1.*", // v5.1.2
        "symfony/flex": "^1.3.1", // v1.21.6
        "symfony/framework-bundle": "5.1.*", // v5.1.2
        "symfony/monolog-bundle": "^3.0", // v3.5.0
        "symfony/stopwatch": "5.1.*", // v5.1.2
        "symfony/twig-bundle": "5.1.*", // v5.1.2
        "symfony/webpack-encore-bundle": "^1.7", // v1.8.0
        "symfony/yaml": "5.1.*", // v5.1.2
        "twig/extra-bundle": "^2.12|^3.0", // v3.0.4
        "twig/twig": "^2.12|^3.0" // v3.0.4
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.3", // 3.4.0
        "symfony/debug-bundle": "5.1.*", // v5.1.2
        "symfony/maker-bundle": "^1.15", // v1.23.0
        "symfony/var-dumper": "5.1.*", // v5.1.2
        "symfony/web-profiler-bundle": "5.1.*", // v5.1.2
        "zenstruck/foundry": "^1.1" // v1.5.0
    }
}

Previous Chapter

Next Chapter