DBIx-Connector-Pool
view release on metacpan or search on metacpan
my ($isbn, $title, $rating) = $sth->fetchrow_array;
# ...
}
);
};
# Description
[DBI](https://metacpan.org/pod/DBI) is great and [DBIx::Connector](https://metacpan.org/pod/DBIx::Connector) is a nice interface with good features
to it. But when it comes to work in some asynchronous environment like
[AnyEvent](https://metacpan.org/pod/AnyEvent) you have to use something another with callbacks if you don't want
to block your event loop completely waiting for data from DB. This module
(together with [DBIx::PgCoroAnyEvent](https://metacpan.org/pod/DBIx::PgCoroAnyEvent) for PostgreSQL or some another alike)
was developed to overcome this inconvenience. You can write your "normal" DBI
code without blocking your event loop.
This module requires some threading model and I know about only one really
working [Coro](https://metacpan.org/pod/Coro).
# Methods
lib/DBIx/Connector/Pool.pm view on Meta::CPAN
my ($isbn, $title, $rating) = $sth->fetchrow_array;
# ...
}
);
};
=head1 Description
L<DBI> is great and L<DBIx::Connector> is a nice interface with good features
to it. But when it comes to work in some asynchronous environment like
L<AnyEvent> you have to use something another with callbacks if you don't want
to block your event loop completely waiting for data from DB. This module
(together with L<DBIx::PgCoroAnyEvent> for PostgreSQL or some another alike)
was developed to overcome this inconvenience. You can write your "normal" DBI
code without blocking your event loop.
This module requires some threading model and I know about only one really
working L<Coro>.
=head1 Methods
( run in 0.326 second using v1.01-cache-2.11-cpan-9b1e4054eb1 )