Implement Java entity classes for DB integration in Spring project

[melihakpinar]

ℹ️ Description

Create Java classes that will serve as entities in our project's database. These classes will be placed in the models directory of our Spring project.

🎯 Tasks

Develop Java entity classes that correspond to the database schema. Each class should be annotated with Spring's @entity and should include fields, constructors, getters, and setters relevant to the database columns. Look at the ER diagram for attributes. (You can see an example here.)

• Implement Users class.
• Implement GuestUsers class.
• Implement RegisteredUsers class.
• Implement Followings Class
• Implement BlockedUsers class.
• Implement Comments class.
• Implement Likes class.
• Implement Dislikes class.
• Implement Posts class.
• Implement Tags class.

[melihakpinar]

A friendly reminder that this issue is a blocker of #82.

[OmerFarukBOUN]

I am implementing the users.

[OmerFarukBOUN]

I have implemented the Users but I am not sure if I did it right. @melihakpinar can you review it?

[melihakpinar]

I have implemented the Users but I am not sure if I did it right. @melihakpinar can you review it?

Sure thanks, could you please create a pull request to backend branch and add me as a reviewer?

[OmerFarukBOUN]

I am not able to push it? I don't know why.

[OmerFarukBOUN]

Fixed and pushed.

[OmerFarukBOUN]

While implementing like and dislike relations, there are two ways to implement these:

1. Define likeID: faster to implement and (userID, postID) tuple can be forced to bu not null and unique but we still use another ID.
2. Define a class which holds userID and postID and define the ID of likes as this class.

Which one should I implement?

[SturmR]

I’d suggest defining likeID, seems simpler and more flexible.

[OmerFarukBOUN]

We have another problem: We do not want a user to like and dislike a post at the same time. I have 3 suggestions but I do not know which one would be better to implement:

1. Use triggers in the database for check
2. Having only one "Reaction" table for like and dislike
3. Check it in a higher place

I am open for other suggestions too

[OmerFarukBOUN]

I’d suggest defining likeID, seems simpler and more flexible.

I have done some research on it and the articles that I have come across with are doing it with defining a class. @melihakpinar @SturmR @Pqrq what are you thinking about?

[OmerFarukBOUN]

I have realized something, we do not hold special ID's for relations. Which means if we use the id method, we would probably have sql issues :/

[OmerFarukBOUN]

For ease of use in the future, i implement them as classes. Finished all the classes. There is a pending pull request.