Re: Adoption of Metabase (was Re: [PEAR-DEV]Re:ComparingADODB with PEAR DB, Metabase andNative MySQL)
| From: | Tomas V.V.Cox | Date: | Sun, 25 Nov 2001 18:38:25 +0000 |
| Subject: | Re: Adoption of Metabase (was Re: [PEAR-DEV]Re:ComparingADODB with PEAR DB, Metabase andNative MySQL) | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-3081@lists.php.net to get a copy of this message | ||
Yavor Shahpasov wrote:
>
> On Tue, 2001-11-20 at 17:05, Martin Jansen wrote:
> > On Tue, 20 Nov 2001 15:32:38 +0100, André Næss wrote:
> >
> > >To me it seems like PEAR is too early in development for use in a
> standard
> > >production enviroment, and the documentation at pear.php.net is
> almost
> > >empty?
> >
> > That's plain wrong :-). There are a lot of PEAR packages that can be
> > used in production systems. The best example is PEAR::DB here: We
> > use it in production systems every day and it works damn good.
> > (I've heard the same from other people.)
> >
>
> I've used PEAR::DB for almos a year now, and except the average glitches
> it works well and it saves me quite some time in coding
>
> but the guy does have a point, PEAR::DB in the mannual Martin :)
>
> There is quite a bit of documentation on pear::db out there (sort of).
> I willing to volunteer on putting some of it together. I know there is
> a skeleton xml available but my docbook skills are a bit non existant,
> how do I compile that to a html file.
>
> TOMAS: Is it ok to use your PEAR::DB tutorials for this
>
Sure Yavor. Only keep in mind that the tutorial has to have the
posibility of being translated and also has to be accesible in the CVS
for me (and of course others) to keep it updated.
Martin, why not put your manual as a pear package? The manual could be
managed as a package without any problem.
BTW: I have the code to highlight the examples of the manual thanks to
Hojtsy Gabor (the other thing that made me be against docbook) and would
be nice if
you could add that for the pear manual (I can explain you how).
Tomas V.V.Cox