Support for Composite Key via @Embeded plus @Id [DATAJDBC-352] #574
Labels
Comments
Lovro Pandžić commented Hello, Jens Schauder, any idea when this might get fixed? Composite keys seem to be a pretty fundamental feature for any persistence layer library. Since there are no workarounds (I don't consider adding a new unique key to a production table because of library limitations a viable workaround), users that do use composite keys can't use Spring Data JDBC |
Jens Schauder commented This is a feature we want to have. Unfortunately we currently can't see far enough in the future to tell when it will happen. |
hi |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
alpet opened DATAJDBC-352 and commented
Enable usage of
@Embdedded
and@Id
together. I see two scenarios here. One would be for read only repositories and the other for the CRUD repository. With respect of the legacy applications very often read only is enough. How would Embedded participate in a query ?One reason to use a lower level persistence framework in my opinion are legacy applications who very often have Composite Keys. Emabling such feature in spring data jdbc would increase the possible users of the framework
13 votes, 14 watchers
The text was updated successfully, but these errors were encountered: