Re: the future of database packages in PEAR

Lukas Kahwe Smith wrote:

Well its actually multiple packages compared to what we have in PEAR. Its essentially a DBAL, an ORM and a few other things at once. It would probably make sense to put it into PEAR as multiple separate packages. Here is an overview: http://swik.net/Doctrine Also PEAR should not be afraid of documented packages ;)

Hehe, somehow it did not come across the way I intended. Documentation is a good thing indeed and that does not make me afraid :) It looks to me like a lot of code is needed to do things, this is what I got from the documentation.

Wouldn't it make more sense for people to support doctrine as one option and not the only one (that is what I understood when you say base PHP5 packages on it).

If you look at our current database package family we essentially have packages build on top of DB/MDB/MDB2 and other that are build on top of DB_Dataobject. Doctrine provides exactly this basis.

I see what you mean now. I understand doctrine does what DB_Dataobject does, is that right ? An example would be a new doctrine datasource for structures_datagrid. Arnaud.