Skip to content

OrmQueryRequest - skip cache put #3722

@dragkes

Description

@dragkes

Hello. Currently, there are two methods in OrmQueryRequest that control whether a query should put to cache: isBeanCachePutMany and isBeanCachePut.
The issue is that isBeanCachePutMany uses transaction.isSkipCacheExplicit(), while isBeanCachePut uses transaction.isSkipCache(). The latter also checks whether the transaction is read-only. I believe both methods should use transaction.isSkipCache() as the current behavior can cause cache pollution when a batch insert is rolled back, because data may already be written to the cache

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions