Re: Re: [PEPr] Proposal for Database::DB_Table

Quick followup:

Or maybe there is a third option. Maybe Paul can fit his stuff into DB_Storage while maintaining BC.

I am good with this if Daniel is.

Just to make clear, I'd still prefer DB_Table be its own thing, but if the only way for the code to be PEAR standard is as part of DB_storage then I'm OK with that. DB_storage is close to but not quite the solution I envision. (Maybe put DB_table in DB as its own class, not as a separate package?) Thanks for your patience. -- Paul M. Jones pmjones@ciaweb.net Savant: the simple alternative to Smarty. http://phpsavant.com/