DBD::Gofer is a DBI database driver that forwards requests to another DBI driver, usually in a separate process, often on a separate machine. It tries to be as transparent as possible so it appears that you are using the remote driver directly. DBD::...

The "rush" policy tries to make as few round-trips as possible. It's the opposite end of the policy spectrum to the "pedantic" policy. Temporary docs: See the source code for list of policies and their defaults. In a future version the policies and t...

DBD::Gofer can be configured via a 'policy' mechanism that allows you to fine-tune the number of round-trips to the Gofer server. The policies are grouped into classes (which may be subclassed) and referenced by the name of the class. The DBD::Gofer:...

Temporary docs: See the source code for list of policies and their defaults. In a future version the policies and their defaults will be defined in the pod and parsed out at load-time....

This is the base class for all DBD::Gofer client transports....

Connect with DBI::Gofer servers that use http transports, i.e., DBI::Gofer::Transport::mod_perl. This module currently uses the LWP::UserAgent and HTTP::Request modules to manage the http protocol. The default timeout is undef (unlimited). The LWP::U...

Connect via DBD::Gofer but execute the requests within the same process. This is a quick and simple way to test applications for compatibility with the (few) restrictions that DBD::Gofer imposes. It also provides a simple, portable way for the DBI te...

The "pedantic" policy tries to be as transparent as possible. To do this it makes round-trips to the server for almost every DBI method call. This is the best policy to use when first testing existing code with Gofer. Once it's working well you shoul...

Without the "url=" parameter it launches a subprocess as perl -MDBI::Gofer::Transport::stream -e run_stdio_hex and feeds requests into it and reads responses from it. But that's not very useful. With a "url=ssh:username@host.example.com" parameter it...

Connect via DBD::Gofer and execute each request by starting executing a subprocess. This is, as you might imagine, spectacularly inefficient! It's only intended for testing. Specifically it demonstrates that the server side is completely stateless. I...

The *BIG WIN* from using Coro is that it enables the use of existing DBI frameworks like DBIx::Class....

DBD::Proxy is a Perl module for connecting to a database via a remote DBI driver. See DBD::Gofer for an alternative with different trade-offs. This is of course not needed for DBI drivers which already support connecting to a remote database, but the...

DBI::DBD::SqlEngine abstracts the usage of SQL engines from the DBD. DBD authors can concentrate on the data retrieval they want to provide. It is strongly recommended that you read DBD::File::Developers and DBD::File::Roadmap, because many of the DB...