On Thu, Aug 26, 2004 at 08:48:42AM -0700, Dean Arnold wrote: > > While this handles async execution, esp. in support of multiconnection > operations relevant to Teradata's parallel nature, > it doesn't really handle async completion notification, and > I'm not certain there's a clean, DBMS-independent way to support > that without using timers, signals, or threads, all of which > may be problematic. > > Also, in many (most?) instances, driver support for Perl threads > may obviate the need for an async API; in fact, I'd prefer to see > driver developers focus first on thread support, since that doesn't > really require any API definitions, and provides much the same > capability.
I agree. > Perhaps DBI layer enhancements to support sharing > handles between threads would be useful as well. See $h->take_imp_data() and that reminds me to expand the Roadmap in relation to take_imp_data and driver support for building handles around supplied 'imp data'. Tim.
