mirror of
https://github.com/doctrine/orm.git
synced 2026-03-24 06:52:09 +01:00
second-level-cache, entity-hydrator throws exception #5119
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @floriansemm on GitHub (May 4, 2016).
Originally assigned to: @Ocramius on GitHub.
I have the following entity:
Creating and persisting of new
GeoinformationMetaDataobjects works fine. When I query the database I get the following error:I use doctrine
v2.5.4with symfonyv3.0.5.@okwinza commented on GitHub (Jun 24, 2016):
same thing with enabled second level cache, sf 2.8.7, doctrine 2.5.4
Any ideas?
@Ocramius commented on GitHub (Jun 24, 2016):
Does this also affect master?
On Jun 24, 2016 04:19, "Oleg Krasavin" notifications@github.com wrote:
@okwinza commented on GitHub (Jun 24, 2016):
Master seems fine.
@Ocramius commented on GitHub (Jul 12, 2016):
Can anyone verify what commit fixes this issue, and link it up with what this issue duplicates?
@yceruto commented on GitHub (Jul 12, 2016):
@floriansemm, @okwinza the "Association cache definition" documentation has a note:
Please, you could to check if this error still occurs adding
@ORM\Cache(usage="NONSTRICT_READ_WRITE", region="geoinformation_region")toAppBundle\Entity\GeoinformationMetaDatatarget entity ??@Majkl578 commented on GitHub (Jul 12, 2016):
Repro test case here: https://gist.github.com/Majkl578/61731254ea9d36f2f32778d357ff4f5b
Bisected fix to commit
e64f44ec9b(doesn't apply cleanly to 2.5.4 though) which refers to https://github.com/doctrine/doctrine2/pull/1555.@floriansemm commented on GitHub (Jul 14, 2016):
@yceruto the error was caused by an other relation. Everything is fine now.
@lcobucci commented on GitHub (Sep 19, 2016):
Does it means that this issue can be closed?
@Ocramius commented on GitHub (Feb 7, 2017):
Closing as duplicate of #6124 unless anybody can create a different failing test scenario (in such case, I'll re-open).