-
Notifications
You must be signed in to change notification settings - Fork 128
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
Support for JPA like features - @ManyToOne, @OneToMany annotations #352
Comments
Can you elaborate on the actual features you would like to see and tell us a bit about your use-case that you're trying to solve? Referencing JPA and a few annotations can span a pretty huge feature space. |
The spring-data-common and spring-data-relational annotations are available for use but are limited. Updating annotations:
New Annotations:
|
Thanks for the details. We do not plan on adding schema generation and lazy fetching isn't an option either as reactive programming does not allow for blocking operations. Introducing additional wrapper types would pollute the domain model for non-blocking, lazy loading. So eager fetching is really the only option. Also, for eager fetching we cannot come up with something beyond the first level of reference as that is basically the limit of joins in queries. Right now, you can model arbitrary subclass hierarchies where you end up with a table per class. However, polymorphic queries are not supported and I expect us not following that path as polymorphic querying introduces a lot of complexity providing only little value. So what really is then left over is the ID generation strategy. |
Can you create a new ticket for ID generation? Closing this ticket as it's too broadly formulated and hard to understand what's left over. |
No description provided.
The text was updated successfully, but these errors were encountered: