in reply to Re^3: Never use Storable to save XS objects
in thread Never use Storable to save XS objects
Well, basically, I don't want to store the database connection at all.
When I store I want the database connection to be ignored (or filtered out), and when I thaw I want the object to use the currently open connection in the application.
I need to store Perl objects, and for some reason I end up with code references in what I'm storing, and my debugging have shown that it is DBI handles.
If you know of a good and generic way to create a Perl object that uses DBI handles for some of it's method, but allow the object itself to be stored via Storable I'm more than open to some pointers to good documentation. There is a good chance that my constructor is designed in a way that I end up with code references that I do not need.