Agreed, this should be fine for the extraction of data - But if the client is looking submitting or changing data to the databases, then the best method would be for the wrapper to have two (or more) concurrent DBI handles with DBI->autocommit disabled. The DBI->commit method could be called after execute statements to all database handles had been issued. While this method isn't as good as internal synchronisation at the database level, it should suffice for most circumstances.

 

Ooohhh, Rob no beer function well without!