So here is what I plan to do since I have heard no replies...
I went ahead and migrated the tests using enhancement+caching to use the
testing runtime enhancement capabilities Luis and I have built. On top of
that I am going to start adding more detailed assertions.
It does seem to me that even
I worry that this stuff may just not work too. The tests that tested this
stuff all expected the the involved entities to be build time enhanced
prior to launching the tests. Which of course they aren't. So all the
tests for enhancement + caching have effectively been skipped for years.
On Fri,
Gah, hit send too soon :)
This comes up because I am working on the idea of lazy attribute fetch
groups. This means that the simple boolean that we used to store is no
longer going to be sufficient. This ties in with the discussion I started
the other day about using attribute indexes versus att
In reworking some of the support for bytecode-enhanced laziness, I started
thinking deeper about this idea of partial caching of such entities.
First and foremost, why do we even allow this? Essentially what happens is
that we allow a user to partially load an entity, and then stick that
partial
