Subject: | Documentation gives incorrect info about Class::DBI |
The POD for this module states that Class::DBI has caching, and that
this can be a problem in multi-process apps. This is not true.
Class::DBI has no caching: the object index feature uses weak references
and will never prevent an object from going out of scope normally. If
something appears to be staying around, it's because of a scoping issue
in your application, not because of the object index.