Glad you liked it!

Great and detailed feedback. Happy you liked it!

Glad it was helpful!

You are most welcome

Glad you enjoyed it!

My pleasure

glad to hear that!

I already have videos about that. Check the playlist Spring workshops

Please add link

My pleasure Don’t forget to share the video 😄

Awesome thank you!

You are very welcome

Glad it was helpful!

Thank you so much 😁

Glad you liked it!

Happy to know your feedback 😁

Absolutely

Happy to know that 🔥

I will consider this idea.

@@BoualiAli yes plz do consider this

@@BoualiAli Please do it

@@inihood i already published a spring security video

Always welcome

My pleasure

Thank you

Happy you liked it. Not sure about sts, but for Intellij it is just ultimate version

Thanks

I really would like to, bit this gonna take so much time. I hope I can do it one day

​@@BoualiAli Really thanks. Stay blessed!

Thanks

Ok next time

Hi there! So, I'm about a month late, and I'm also just getting started with coding, but I solved this situation last week. In ManyToMany relationships, the intermediate table is generated automatically, which means you can't easily add more attributes without modifying the relationship itself. The only way I found to resolve this involves actually not using ManyToMany but setting up two OneToMany relationships between employees/missions on the "One" side, linking them to a third entity that contains both IDs along with any extra attributes. Using an example, this would be represented by the EmployeeMission class, which includes employeeId, missionId, and createdAt attributes. As Ali shows here, for OneToMany relationships, it's important to specify the "mappedBy" annotation, and I also found it helpful to specify the fetch type. I hope my explanation is clear and helpful. Have a great day!

My pleasure

Already have one about spring security. Check it in the same playlist

@@BoualiAli I did and it is an absolute honour to even talk to you. Where can I reach u out to talk further?

@@kevinameda2711 the honor is mine You can reach me on our discord server

if you don't have any extra fields, you don't need to

Why your app is not starting after adding one to one? Can you provide some logs in the discord server (screenshots) to make easier to understand

@@BoualiAli Yeah I noticed on one to one bidirectional it is better not to provide mapped by on one entity otherwise,otherwise there’s only one foreign key like unidirectional

It depends on the logic and needs for your application

Unidirectional Relationship: This means that one entity has knowledge of the other, but not vice versa. In other words, if you have two entities, say EntityA and EntityB, and if EntityA has a reference to EntityB (but EntityB does not have a reference to EntityA), then it's a unidirectional relationship. Unidirectional relationships are simpler and less complex, and are suitable when there is no need for the referenced entity (EntityB in our example) to know about the entity that is referencing it (EntityA). For instance, if you have a User entity and a Profile entity, and each User has one Profile, but a Profile does not need to know which User it belongs to, you can model this as a unidirectional relationship from User to Profile. Bidirectional Relationship: This is when both entities are aware of each other - EntityA has a reference to EntityB, and EntityB also has a reference to EntityA. This kind of relationship is a bit more complex due to the need to keep both sides of the relationship in sync. Bidirectional relationships can be useful when there is a need for both entities to be aware of each other. For example, if you have a Customer entity and a BankAccount entity, and each Customer has one BankAccount, but a BankAccount also needs to know which Customer it belongs to, then you would model this as a bidirectional relationship.

when creating an employee you need to set the department object and pass the department is Here is an example Department dep = new Department() dep.setId(departmentId) // the one you get in your request / object / param (depends how you get it) Employee emp = new Employee() emp.setField() emp.set....() emp.setDepartment(dep) repository.save(emp)

Happy you liked it! Soon

aliboucoding.com/courses

You need to create an extra entity that will hold the relation and the extra fields as well

@@BoualiAli could you please create video about that?

@@kamilleskamilless8113 about what exaclty?

Thank youu

Welcome

Will note that for the next video

Object by default is null Premitive like int by default 0 You null on the id to help hibernate well manage the entities. Checkout my new course about spring data jpa and you will understand all this details and master this topic aliboucoding.com/courses

Bacause we use ArrayList type field to hold MANY objects, Since ArrayList implements List interface that SUPPORTS only OBJECT TYPE not the primitive type

Spring Data JPA | Hibernate kzfaq.info/sun/PL41m5U3u3wwkS8BU0fIeRQwY3hK4VlFlX

yes

Thank you too!

Hi, can explain your question? I didn’t understand

@@BoualiAli how to use join query in spring data jpa, use Employee_Id and get: Employee Info and his address and his Mission and his Department. thank you in advance for your reply. 😀

How is that possible? Can you share some screeshots and code snippets on the discord server?

It was already explained in the beginning of the video

Pourquoi?

@@BoualiAli suivant la cardinalite que vous mentionné dans votre diagramme de class.

@@miloudseo7883 peux tu expliquer plus?

@@BoualiAli clé étranger de la table employee doit etre dans la table départemant car un employee appartient à plusieurs départemant, et chaque départemant ayant une seul employee(ma raisonnement suivant la cardinalité que vous avez mentionné, en uml en raisonne comme ca)

@@BoualiAli je crois tu dois changer la cardinalité entre table employee(*) et departemant(*) to ManyToMany