Skip to content

Conversation

@Vidal322
Copy link
Contributor

@Vidal322 Vidal322 commented Oct 11, 2025

Closes #179

Review checklist

  • Behavior is as expected
  • Clean, well structured code
  • Properly documents API changes in the corresponding controller test
  • Contains enough appropriate tests
  • Changes are reflected in the Wiki if necessary

@Vidal322 Vidal322 linked an issue Oct 11, 2025 that may be closed by this pull request
var password: String,

@ManyToMany(mappedBy = "teamMembers", fetch = FetchType.EAGER)
// @JsonIdentityReference(alwaysAsId = true)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// @JsonIdentityReference(alwaysAsId = true)

joinColumns = [JoinColumn(name = "activity_id")],
inverseJoinColumns = [JoinColumn(name = "account_id")]
)
@OrderColumn
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ideally, both teamMembers in the Activiy model and the hallOfFame in the Project model should be of type MutableSet. This way we won't need the @OrderColumn annotation. This can be a little tricky to do, but it will increase the performance, since it will eliminate these unnecessary index management in the database.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

activities: change team relationship to ManyToMany

3 participants