RE: [PEAR-DEV] ezSQL
| From: | Lukas Smith | Date: | Wed, 23 Oct 2002 08:43:00 +0000 |
| Subject: | RE: [PEAR-DEV] ezSQL | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-10209@lists.php.net to get a copy of this message | ||
> From: Vincent, Justin [mailto:J.Vincent@elsevier.com]
> Sent: Wednesday, October 23, 2002 10:32 AM
> To: 'Alan Knowles'; smith@dybnet.de
> Cc: pear-dev@lists.php.net
> Subject: RE: [PEAR-DEV] ezSQL
>
> > Actually it looks closer to DB_DataObject, than pear, - If
> > this was to
> > go in, it would be best implemented as a wrapper to pear:DB or MDB.
> >
>
> Yes. Exactly. A wrapper for pear:DB that is what I
> was thinking of.
Well you could write a custom result object for PEAR DB.
This feature was dropped from MDB for performance reasons.
> BTW - 650 people have downloaded it since last Wed. so I think it
> is doing something in a way that users find very useful.
>
> I have also had feedback that the documentation makes it very
> easy to use.
>
> http://php.justinvincent.com
>
> People also seem to like the fact that it is very small
> API with not too many functions.
Hmm well they way you implemented it the main goals seem to be
minimizing code length and easy learning curve by reducing everything to
a small and compact set of methods.
I think most of what you want to do can be achieved by providing an
alternative result object for PEAR DB (which should be possible with
PEAR DB iirc). And a small API can just be a question of documentation
:-)
I will look if it can be made an optional feature to get a result object
instead of a result resource in MDB without too much of performance
loss.
Regards,
Lukas