Mark Scherer

Yeah, I think we would need to open this up for such an interface approach maybe? Is that too out of scope? Our current solution is IMO too simple for...

The way symfony solved this seems to be a [TagAwareAdapter](https://github.com/symfony/symfony/blob/7.2/src/Symfony/Component/Cache/Adapter/TagAwareAdapter.php) and the two dimensional approach of cache adapters > it needs one or two cache adapters: the first required one...

It would also be nice if we then adopted the idea of built in [Stampede prevention](https://en.wikipedia.org/wiki/Cache_stampede). > instead of waiting for the full delay before expiring a value, recompute it...

If we didnt plan on adding more serious cache functionality, I guess it would be simple enough to just re-use symfony components here. ```php // src/Service/SymfonyCacheService.php namespace App\Service; use Symfony\Component\Cache\Adapter\RedisAdapter;...

> This seems simpler to implement, as it could be a setting on the engine. Then I guess we could just focus on that part for now. That also seems...

I agree with you. Did you manage to track down the issue? And maybe provide a fix as PR?

The main issue seems to be that the marshaller first validates on the whole dataset, then looks into fields config ```php $entity->setErrors($errors); if (!isset($options['fields'])) { ``` I would also expect...

One option could be ```diff Index: src/ORM/Marshaller.php IDEA additional info: Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP UTF-8 =================================================================== diff --git a/src/ORM/Marshaller.php b/src/ORM/Marshaller.php --- a/src/ORM/Marshaller.php (revision 4b8915cf32949cac5c798af2ff65f688c4d76d21) +++ b/src/ORM/Marshaller.php (date 1744566492371) @@ -286,13 +286,21 @@...

cc @menshutin

ping @jamisonbryant Is this still something you want to PR?