Remove the need for relationship repositories
See original GitHub issueThe title says it all. I have brought this up and it’s been discussed, but I am making it an official issue so we can continue to conversation and throw some code around on how to do it.
Once you have a Repository<Something,Long>
you don’t need anything else. And I am pretty sure the Long
can go to.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Delete fork dependency of a GitHub repository - Stack Overflow
Show activity on this post. Go to the repository that you need to detach: https://<ghe url>/<org>/<repo> Click on the “Site Admin” rocket on...
Read more >Provide option to remove fork relationship when forking project
Problem When forking a repository, users cannot immediately remove the fork relationship when forking. Users must go into project settings ...
Read more >Using database tools to remove relationship instance ... - IBM
You can use database tools to manually delete all of the database artifacts that comprise a relationship, including tables, stored procedures, and sequences....
Read more >Did you completely remove secrets from git repository? Really?
Removing secrets from git repo is straightforward. With help of BFG Cleaner and privileges to force push the modified history, ...
Read more >Spring Data JPA Delete and Relationships - Baeldung
As we know from the Spring Data JPA reference documentation, repository interfaces provide us some basic support for entities. Let's say we have...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think @remmeier has good point here. And if combine both of those approaches we will find ultimate solution. So having out of the box relationship repositories with possibility to override the generic implementation for more complex solutions seems perfect to me. 👍
note that some further improvements to ResourceUpsert are tracked by https://github.com/katharsis-project/katharsis-framework/issues/130.