Re: the future of database packages in PEAR

I've not had a chance to look at Doctrine, I've got no objections for it going into PEAR. From DataObjects point of view, I have the PHP5/PDO version lying around somewhere, that was done by Klaus (AFAIR), This is really the direction DataObjects needs to go, however, the crunch is that my major client can not upgrade their servers to PHP5. Cost/time etc. so even new projects for them still tend to be done with PHP4. Hence testing and improving on the PHP5/PDO DataObjects is not currently on the radar (however much I'd like it to be...) Maybe this will change next year. Regards Alan Lukas Kahwe Smith wrote: > Matt Friedman wrote: > >> From: >> http://www.phpdoctrine.com/documentation.php?index=1.6#1.6.4 >> Composite >> Composite primary key can be used efficiently in association tables >> (tables that connect two components together). It is not recommended >> to use composite primary keys in anywhere else as __Doctrine does not >> support mapping relations on multiple columns__. >> >> DB_DataObject suffers from the same issue. It would be great, if pear >> is indeed going to adopt Doctrine as a pkg, if Doctrine resolved this >> issue. > > This should be solvable. Its exactly this kind of stuff where I think > we can give the author of doctrine a helping hand. > > It would be nice if the current people working on Database related > stuff speak up (Justin, Alan, Mark, David) on their take. > > regards, > Lukas >