I see what your saying now I think:
Code:
class Authors extends Zend_Db_Table_Abstract {
//table definition
}
class Author extends Zend_Db_Table_Row {
//individual record from Authors table
}
I guess there's nothing wrong with that, but it would only really be necessary if you need to alter to default behavior of Zend_Db_Table_Row. Anything you pull out of a Zend_Db_Table object will be of type Zend_Db_Table_Row or Rowset. If you query straight off the db adapter you'll get arrays mostly.
I currently have a project underway that connects to no less than 6 different dbs on 4 diferent servers, and we're just dealing with infrastructure at the moment, no real function pages have been producted... so yes is very possible within the enterprise to have a set of db adapters as apposed to a single adapter.