> I¹m unsure as to why this code/data combo used to work in version 1.2.2 and
stopped working in 2.x
This sounds somewhat familiar, but I'm unable to find any posts on the
mailing lists. My best guess is that in 2.x we may have found a bug where
we weren't properly enforcing fetch depth... but that
Hi Rick,
Thanks for your suggestions. The good news is that I managed to determine
what was causing the issue.
The bad news is that it turns out, that despite my best intentions, that
many of my initial diagnoses
and thoughts were quite wrong.
So - the parts that were incorrect:
Initially, I th
A couple quick thoughts/debug suggestions for you :
- Can we get a copy of your persistence.xml file?
- Can you try to run with 2.0.x to see if something was introduced in the
original 2.0 implementation effort, or if it came sometime after?
- Have you tried setting your fetch graph to be entirely
Apologies for the double send. I thought the first message had been spam
filtered by the mail-bot, but apparently it was only delayed.
Jeff Oh, Sr. Software Engineer
Phone: 604.408.8078 ext. 104
Email: jeff...@elasticpath.com
Elastic Path Software Inc.
Web: www.elasticpath.com
Blog: www.getel
Hello All,
We've recently upgraded to 2.3.0 (from 1.2.2) and have encountered a nasty
bug where when loading a complicated cyclic object graph using a fetch
group, some relationships are not being populated under some circumstances.
Unfortunately, the graph really is quite complicated, and while
Hello All,
We've recently upgraded to 2.3.0 (from 1.2.2) and have encountered a nasty bug
where when loading a complicated cyclic object graph using a fetch group, some
relationships are not being populated under some circumstances.
Unfortunately, the graph really is quite complicated, and whil
