Skip to content

Incorrect transaction cache lookup result for find(Set<Id>) with composite key #128

@akozlovskiy

Description

@akozlovskiy

Description:

When using a composite key consisting of multiple fields, transaction cache lookup returns incorrect results for find(Set).

Steps to Reproduce:

Within a transaction, insert multiple records where the first field of the composite key has the same value.

In the same transaction, attempt to retrieve these records using find(Set).

The method does not return the expected records.

However, if searching within the same transaction using find(Id) with all fields of the composite key fully specified, the record is correctly retrieved from the transaction cache.

Expected Behavior

find(Set) should correctly retrieve records from the transaction cache, just like find(Id).

Actual Behavior

find(Set) returns an incorrect result (missing records that were inserted earlier in the transaction).

find(Id) with a fully specified composite key correctly retrieves the record from the cache.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingresearch

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions