This patch also fixed issues where I was having to manually force an entity to be reloaded from the database to reflect changes. I was able to comment out changes I'd made just to get my project working under 3.1, and all of project tests now pass.
Even if we decide to drop "use shared cache" at some point, I think it's worthwhile to commit this patch for 3.1, and possibly 3.0. Any reason why I should not do so? I'd like to also write a Cayenne test showing the issue, but I probably won't get to that until late this week. On Mon, Nov 4, 2013 at 11:30 AM, Mike Kienenberger <[email protected]> wrote: > On Mon, Nov 4, 2013 at 2:16 AM, Aristedes Maniatis <[email protected]> wrote: >> We experimented with that option and unticking it caused expected behaviour >> that was quite hard to understand. Particularly in how it inter-related to >> the object >> cache. Dima is the person who knows all the details of that experiment. > > I think the fix to CAY-1880 might be all that's needed to make this > usable. The issue would certainly explain the unusual behavior you > were seeing.
