How to model relationships (1-1, 1-m, m-m)

[@dylanroberts9351]

I was impressed by the exceptionally clear and to-the-point descriptions of the different relationships - well done!

[@PrismaData]

Glad you enjoyed it!

[@raphaelfreitas4565]

That's what we need! A simple and concise yet complete and clear explanation and examples of a subject...

[@frozen_tortus]

Woa, this is some down to the point video, time not waisted watching this. Thanks. Sabin needs a raise, this is so much better then I remember how other guy did it.

[@nomanaslam8648]

I appreciate your work dude. it's definitely too the point and very much time saving.

[@granfalloner]

Thank you for concise presentation! One clarification, though - it seems that one-to-many relationships is a bit wrong - `@unique` annotation for `userId` in `Post` model would actually preclude single user from having multiple posts, so this annotation probably needs to be removed.

[@saurabh75prakash]

Hi, thanks for your input. Can you please point me to the document where this concept is discussed.

[@pandonia77]

You are correct. the @unique attribute needs to be removed otherwise this is a one-to-one

[@lehung5914]

Simple and straight forward!. Thanks

[@andrewking1173]

So simple and straight to the point, thanks!

[@josippardon8933]

In 1:31, are you sure this is one-to-many? You put @unique for userId in Post. This means that in Post table only one row with certain userID can exist, which implies that for specific user only one post can exist.

[@patrick_kabwe]

Thanks, Sabin.
Looking forward to the self-relation video

[@PrismaData]

Coming soon!

[@devali1430]

These shorts are the best

[@prateekster]

Clean explanation, thanks

[@gbubemijohn7183]

thank you for this , you saved my life

[@CodeHassanX]

great video sir, keep up

[@Blue-bb9ro]

VERY clear to follow along, thanks

[@lordfranktex5270]

I appreciate your effort.

[@startup_dream]

Wow, what a tremendous video. Well done!
I would like to have seen a video where you also explain the different prisma functions, such as findMany, findOne etc.. written in code, intertwined with the use if these different model relations.
Maybe there is one, will look through the channel.

[@belkocik]

Straight to the point! However, diagrams would be helpful :)

[@heliosweb]

Gonne be super helpful! Thanks!

[@yassinebouchoucha]

thanks for the clarification, how can we have multiple prisma schema definition under the same repo/project !?

[@gitlit5489]

I think one-to-many had a problem, the ‘userId’ should not be unique, because more than one post can be related to the same user a.k.a. the same ‘userId’

[@happydaydaniel]

Thanks for the video. Please, which relationship is best to create a relationship between Wishlist, user and products?

[@BharatBhandari-s5i]

Brother, In 1-m realtionship model the userId in Post model is @unique
as 1 user can have multiple post so userId can repeat right?, so it shoudn't be unique

[@yunhanhuang9304]

Does it mean that we'd better use the implicit one to keep the prisma config file clear?🤔

[@PrismaData]

👋🏽
This would be dependent on your use-case. You can create an explicit m-n relation to add more fields to the join table.

[@fotoflo]

Are there any performance implications of implicit m-m relationship?

[@zaighumhassan7398]

Thank you man ❤

[@SupertigerDev]

Is there something like this? With postgresql
Role {
userIds: String[]
users: User[] @relation(field: 'userIds', references: 'id')
}

[@mohamadrezakazemian5220]

good explanation

[@diegomedina2359]

4:15 why would be good to handle the relation table by oneself?

[@aiune2764]

@PrismaData, isn't it a violation of the constraints to define userId as @unqiue---00:01:23?

[@raimundoneto4557]

muito bom mano. parabéns pelo trabalho.

[@samuelerbo]

Thanks.

[@PensoMuito]

and create action, how can i do?

[@Mahendrashah-sm1om]

hey, Does anybody knows how to seperate prisma model in different files?

[@jesusidev]

With the include to get the name instead of just id's you can do something like this:
include: {
tags: {
include: {
tag: true,
},
},
},

[@expeng5861]

my brain already stackoverflow.

[@nirmitjatana1245]

To the point 👍

[@expeng5861]

greate man

[@killerdroid99]

I thought you were Ben awad for a sec

[@edwknvlv]

Please dont overlap code with your face))

[@nextebiz6897]

good, thank you boy

[@brenosantin9739]

i cant find in prisma docs about a zero to many relationships, can somebody help me?
model infonutriday {
id String @id @db.VarChar(45)
date DateTime @db.Date
portion Float @db.Float
protein Float @db.Float
calories Float @db.Float
grease Float @db.Float
salt Float @db.Float
finalizedDay Int @db.TinyInt
meals Meal[]
foods Food[]
infonutriday_has_users infonutriday_has_users[]
}
model Food {
id Int @id @default(autoincrement())
name String
portion Int
protein Float @db.Float
calories Float @db.Float
grease Float @db.Float
salt Float @db.Float
image String?
infonutridayId String?
infonutriday infonutriday? @relation(fields: [infonutridayId], references: [id])
meals_has_foods meals_has_foods[]
users_has_foods users_has_foods[]
@@map("foods")
}
model Meal {
id Int @id @default(autoincrement())
name String
isMeal Int @db.TinyInt
portion Int
protein Float @db.Float
calories Float @db.Float
grease Float @db.Float
salt Float @db.Float
image String?
infonutridayId String?
infonutriday infonutriday? @relation(fields: [infonutridayId], references: [id])
meals_has_foods meals_has_foods[]
users_has_meals users_has_meals[]
@@map("meals")
}
Infonutriday can have 0 or many foods or infonutriday can have 0 or many meals.
Any suggestion ?

[@lordfranktex5270]

Thanks.