).
Anyway, I'm caching the connections under a key I'm constructing just like
`connect_cached()` does:
my $key = do {
no warnings 'uninitialized';
# XXX Change in unlikely event the DBI changes this function.
join !\001, @_[0..2], DBI::_concat_hash_sorted
like `connect_cached()` does:
my $key = do {
no warnings 'uninitialized';
# XXX Change in unlikely event the DBI changes this
function.
join !\001, @_[0..2], DBI::_concat_hash_sorted(
$_[3], =\001, ,\001, 0, 0
David E. Wheeler wrote:
I've just released
[DBIx::Connector](http://search.cpan.org/perldoc?DBIx::Connector) to the
CPAN. It does connection caching and transaction management, borrowing
pages from `connect_cached()`, Apache::DBI, and DBIx::Class, but usable
in any of these environments. The
On Oct 5, 2009, at 5:41 PM, Darren Duncan wrote:
But from what you've described in your blog to be the state of
affairs, I think that having a distinct DBIx::Connector module is a
good idea, versus embedding that functionality in a larger DBI-using
module.
Yes, that's the idea.
I've