DBIx-Poggy

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

            die $error;
        })
        ->finally(sub {
            $cv->send( $res );
        });

        $cv->recv;

DESCRIPTION
    "Async" postgres as much as DBD::Pg allows with Promises instead of
    callbacks.

    You get DBI interface you used to that returns promises, connections
    pool, queries queuing and support of transactions.

  Why pool?
    DBD::Pg is not async, it's non blocking. Every connection can execute
    only one query at a moment, so to execute several queries in parallel
    you need several connections. What you get is you can do something in
    Perl side while postgres crunches data for you.

lib/DBIx/Poggy.pm  view on Meta::CPAN

        die $error;
    })
    ->finally(sub {
        $cv->send( $res );
    });

    $cv->recv;

=head1 DESCRIPTION

"Async" postgres as much as L<DBD::Pg> allows with L<Promises> instead of callbacks.

You get DBI interface you used to that returns promises, connections pool, queries
queuing and support of transactions.

=head2 Why pool?

DBD::Pg is not async, it's non blocking. Every connection can execute only one query
at a moment, so to execute several queries in parallel you need several connections.
What you get is you can do something in Perl side while postgres crunches data for
you.



( run in 0.252 second using v1.01-cache-2.11-cpan-9b1e4054eb1 )