On Fri, Dec 30, 2005 at 12:58:02PM +0100, wernerus sebastien wrote: > Tim, I made the changes you suggested. Here is the code: > -------------------------------
Thanks. > ------------------------------- > > But it gives exactly the same result, namely: > connection ok > test1: > test2: Umm. [...later...] Ah. The current t/30subclass.t test doesn't check that connect was called, and it isn't. And that's by design (I think :) To intercept the connect you can override one of these two methods: - MySubDBI::connect - MySubDBI::db::connected Tim.
