view release on metacpan or  search on metacpan

README  view on Meta::CPAN

            # don't retry for errors that don't include "server" in the message
            return undef if $drh->errstr !~ /server/i;
    
            # or return a hash ref containing the retry options to use
            return { ... };
        };

DESCRIPTION

    The DBIx::RetryConnect module arranges for failed DBI connection
    attempts to be automatically and transparently retried for a period of
    time, with a growing delay between each retry.

    As far as the application is concerned there's no change in behaviour.
    Either the connection succeeds at once, succeeds sometime later after
    one or more retries, or fails after one or more retries. It isn't aware
    of the retries.

    The DBIx::RetryConnect module works by loading and monkey patching the
    connect method of the specified driver module. This allows it to work
    cleanly 'under the covers' and thus avoid dealing with the complexities

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

        # don't retry for errors that don't include "server" in the message
        return undef if $drh->errstr !~ /server/i;

        # or return a hash ref containing the retry options to use
        return { ... };
    };

=head1 DESCRIPTION

The DBIx::RetryConnect module arranges for failed DBI connection attempts to be
automatically and transparently retried for a period of time, with a growing
delay between each retry.

As far as the application is concerned there's no change in behaviour.
Either the connection succeeds at once, succeeds sometime later after one or
more retries, or fails after one or more retries. It isn't aware of the retries.

The DBIx::RetryConnect module works by loading and I<monkey patching> the connect
method of the specified driver module. This allows it to work cleanly 'under the
covers' and thus avoid dealing with the complexities of C<connect_cached>,
C<dbi_connect_method>, C<RaiseError> etc. etc.