Ok, done

Anyone else?

<:boomer:480046032546168863> 😎

Urself @porco

@fedora

Something like this

Ok, !sudoku

Trying to figure out how to write that in Doctrine

I don't know much about doctrine but maybe just Google "Doctrine one to many relations"

Though that covers only one array part of the entity

For the second one I have no fucking clue, might just leave it as a long ass string

https://www.doctrine-project.org/projects/doctrine-orm/en/2.6/reference/association-mapping.html

Since I want user to write a step by step guide, thought neat way of doing that would be by making each step an array member

But I might just go full lazy and make a textarea so user will write a longass string there

You should probably reconsider your database design if you run into this kind of problems. Make a ERD

>any planing whatsover

We do shit as we go

Then let someone validate your ERD

lel

That sure will be a great product

Not much to ERD about tho

Since right now I got 3 entities top

User, Recipe, Ingredient

If you are considering putting arrays in your database, you really should make an ERD

Believe me

1 user = many recipes
1 recipe = many ingredients

And that covers all my ERD needs

Ok pro

So yeah, guess One-To-Many should work

Thanks

Just don't complain when it sucks

I'm not sure I already said it but

Or when it becomes unmaintainable

I'm not planning on maintaining it or making cash out of it or whatever

I'm just planning to make it, write doc about it, turn that shit to uni

And make them make me an engineer

Don't overwork yourself for no reason, I like it

https://en.wikipedia.org/wiki/Thesis#Poland

If I were doing this for fun, I sure as hell wouldn't be doing a fucking website or webapp or whatever the fuck you call this

!bible