Hello,
There are many subtleties in doctrine that I don't understand.
But why the collection cache is based on an key that involve rootEntityName ?
For instance how does it works in the following case:
#[Entity] // <--- Some entity declaration using discrimination map
class CommonClass {}
class ExtendedClassA extends CommonClass
{
#[ManyToOne...]
protected $attribute;
}
class ExtendedClassB extends CommonClass
{
#[ManyToOne...]
protected $attribute;
}
The code below should be computing a key that is something like : "commonClass_XX_attribute" in both cases and so this might conflict right ? (I am looking for a second level cache issue in one application and that's how I end up here)
|
return new CollectionCacheKey($metadata->rootEntityName, $association['fieldName'], $ownerId); |
This is actually same for timestampKey, right ?
|
$this->timestampKey = new TimestampCacheKey($this->class->rootEntityName); |
Thank you for your help :o)
Hello,
There are many subtleties in doctrine that I don't understand.
But why the collection cache is based on an key that involve
rootEntityName?For instance how does it works in the following case:
The code below should be computing a key that is something like : "commonClass_XX_attribute" in both cases and so this might conflict right ? (I am looking for a second level cache issue in one application and that's how I end up here)
orm/lib/Doctrine/ORM/Cache/Persister/Entity/AbstractEntityPersister.php
Line 610 in ed56f42
This is actually same for timestampKey, right ?
orm/lib/Doctrine/ORM/Cache/Persister/Entity/AbstractEntityPersister.php
Line 97 in ed56f42
Thank you for your help :o)