Fetching entities with Composite Key Relations #8425
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In our database design we are using entities with composite keys, and we are using composite keys relations between entities.
Let say we have the following entities with Primary Keys (PK):
Company
(PK:company_code
)Customer
(PK composite:company_code
+customer_code
)Invoice
(PK composite:company_code
+invoice_code
)and the following relations in
Invoice
:Company
(usingcompany_code
), not nullableCustomer
(using composite keycompany_code
+customer_code
), nullableNow we have
company_code
(not null) but nocustomer_code
(null).We want to fetch
Invoice
entity, so that we get not nullCompany
, and nullCustomer
.The problem is that loading
Invoice
with nullCustomer
is not working - we are getting the following exception:This PR provide a fix, to load the
Customer
in the described case.The change is pretty simply, and no other tests are affected.
NOTE: Loading
Company
is not a problem as it is using relation on just one column (not a composite key). The description includes it just for completeness of the example.