Re: Re: [PEPr] Proposal for Database::DB_Table
| From: | Daniel Convissor | Date: | Thu, 08 Jan 2004 02:57:42 +0000 |
| Subject: | Re: Re: [PEPr] Proposal for Database::DB_Table | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-24879@lists.php.net to get a copy of this message | ||
Lukas and Paul:
On Thu, Jan 08, 2004 at 12:07:09AM +0100, Lukas Smith wrote:
>
> Or maybe there is a third option.
> Maybe Paul can fit his stuff into DB_Storage while maintaining BC. This
> would breath new life into code that was left to bitrot more or less.
It doesn't matter to me what happens. I haven't used, let alone even
really looked at the DB_storage subclass. Nor have I taken a look at
Paul's proposal.
So, I don't have any insights as to how the two may or may not fit
together. If they're so similar, then sure, use Pauls concepts to enhance
storage.php. But you're mentioning efforts to maintain compatibility.
If there are going to have to be lots of contortions to have
compatibility, it might be best to make it a separate subclass in DB.
So, in short, it doesn't really matter to me what y'all decide.
Enjoy,
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409