Re^2: Setting up database connection in tests

[Tanktalus]

I suppose something could be attempted on some operating systems of opening the DB handle in a wrapper process, setting it up to be passed through some IPC method, and launching your test script once that setup is complete. It seems to me that this would be very fragile and too clever to maintain.

Actually, that pretty much sums up DBD::Proxy. Not fragile at all, but precisely a piece of the core DBI package. And, for extra example code, see Coro::DBI (which cannot install via cpan only because the only release is a "developer" release though it has worked fine for me with the CB stats).

[MidLifeXis]

Is DBD::Proxy setting up a single connection and then passing it to each test script, as asked by the OP (thinking along the lines of passing a file handle between various scripts), or is it setting up a meta-connection, where a connection to a DBI::Proxy connection is talking to another DBI connection through, well, a proxy?

This approach is different than what I was considering, and does make some good sense. An approach that I had not considered!

Update: Reading through the documentation for DBI::Proxy, I am not certain that it meets the needs of the OP's third requirement - connecting once to the database and being able to run all of the test scripts. Perhaps it is just my unfamiliarity with the Coro method of doing things. Would you have a more complete example that implements something along what the OP was asking?