in reply to
Re^4: How should a fork of DBIx::Simple be handled?
in thread How should a fork of DBIx::Simple be handled?
Are you going to call your fork DBIx::Simple::CircularReferences or DBIx::Simple::NeverDestroys?
and tye tried it and saw the problem
What I "saw" was that you should simply stop writing code that destroys the container object if you want to keep using one of the contained objects. But you insist on making a simplistic change to the DBIx::Simple module and not making a trivial change to how you use that module, even after I made it quite clear that your proposed change breaks the lifecycle management of the module.
Unless you proposed a patch that fixed your "bug" without creating circular references, I would make the next "movement on the RT" to close it as "working as designed".