-
Notifications
You must be signed in to change notification settings - Fork 350
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
Add support for @JoinColumn #1952
Comments
Hmmm... @schauder , is there anything I can do in order to push my Feature request? |
Most of the time I'd say provide a PR, but currently I'm working on a feature that changes a lot of stuff in the areas that would be touched by a PR. Such a PR would therefore run into a lot of conflicts. But if you wait until said feature is done, a PR would be welcome, but probably quite challenging. |
Of course I can wait @schauder. The first question for me: is the feature request itself reasonable ? what do you think? |
Yes, I do think this is absolutely reasonable. |
I am new to Spring Data JDBC. If there is support for |
There is no support for |
@schauder Thanks for providing the references. I got the idea of aggregates with root entities. But I have one query if you are happy to answer it.
I know, it is not possible to persist data based on these mappings. But technically, we can get the data from entity mapping the common column if @joincolumn is implemented in the future. Please correct my understanding if I have misunderstood anything. |
No. A mapping like this will still either cause a stackoverflow or some custom error due to a recursive definition of an aggregate. |
Thanks @schauder, I got your point related to the bi-directional mapping. I got your answer from stack overflow that as per Spring boot JDBC implementation, it will fetch all information at the same time and doesn't have Lazy Loading principle. 😊 |
Hi,
I love the simplicity of
spring-data-jdbc
, but sometimes it feels too restrictive compared to possibilities of JPA. I miss the@JoinColumn
feature.Please let me describe my need for it
I have use cases, where relations are either based on that unique field/property/column or on another unique field/property/column.
I tried to use the
NamingStrategy
to achieve my goal, but it didn't work either.best regards
The text was updated successfully, but these errors were encountered: