blaze-persistence
blaze-persistence copied to clipboard
[#1722] avoid NPE in TupleTransformatorFactory
For some unknown reason a classMappingIndex sometimes points to a non-present field in the tuple (filtered via fetches mechanism). The correct fix should be somewhere else but that this is probably good enough - just don't perfomr any tuple transformation for non-present fields.
Also, fix a small bug in hasSubFetches. The wrongly implemented equality check lead to overfetching.
Description
Related Issue
Motivation and Context
Can you please add a test case that reproducers this issue? I'd like to make sure we don't reintroduce such a regression again.