Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move hashtags to own entity #194

Open
florianschmidt1994 opened this issue Apr 23, 2017 · 0 comments
Open

Move hashtags to own entity #194

florianschmidt1994 opened this issue Apr 23, 2017 · 0 comments
Assignees

Comments

@florianschmidt1994
Copy link
Member

Hashtags should be an own entity, because the use-case always dictates that hashtags are used for search and nothing else.
The information about an hashtag is also included in the text of a posting, so there is no need for it to be transferred as a list seperatly

PostingService.findByHashtag() --> HashtagService.findPostingByHashtag()

Applied principle: Try to avoid unnecessary one-to-many associations and instead use many-to-one with different repositories.

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

No branches or pull requests

2 participants