fix: Error when using with
when the child references a parent but not using the parent's id column, but rather another column that is a unique index.
#1902
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.
EntityID
, a "is not in record set" error occurs becauseentities.groupBy { it.readValues[parentTable.id] }
should beentities.groupBy { it.readValues[refColumn] }
instead.refColumn
, we attempt to store the referenced column value in the cache, which does not compile because it's not the right type expected bycache.getOrPutReferrers
, so we need to find the parent entity that matches the value of the refColumn and use its entityId to store it in the cache.findById
, which was being invoked onthis
, which is the child entity, usingid as EntityID<ID>
which is for the parent entity. The fix is to find the child entity by usingrefColumn
, which is the column in the child table that references theid
in the parent table.