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

JPA specialization [Proposal] #143

Closed
otaviojava opened this issue May 4, 2023 · 2 comments
Closed

JPA specialization [Proposal] #143

otaviojava opened this issue May 4, 2023 · 2 comments
Labels
design Improvements or additions to design documentation Improvements or additions to documentation enhancement New feature or request

Comments

@otaviojava
Copy link
Contributor

The goal is to isolate the CrudRepository and Repository to work with any persistence engine instead of JPA.

Currently, our documentation is more guided to JPA, and one way to solve it is to create a specialization.

This way, we can keep the details of JPA/JDBC in place without impacting the core idea of the Data that is more agnostic than we have now.

@otaviojava otaviojava added the bug Something isn't working label May 4, 2023
@keilw keilw added enhancement New feature or request documentation Improvements or additions to documentation design Improvements or additions to design and removed bug Something isn't working labels Sep 1, 2023
@gavinking
Copy link
Contributor

This can easily be done as part of #470.

@otaviojava
Copy link
Contributor Author

This can easily be done as part of #470.

Nice, I will close this one here to focus on the next one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Improvements or additions to design documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants