Re: [Phpgroupware-developers] phpGroupWare and PEAR db abstraction layers

[Chris Weiss]

not sure where the confilct lays.  I know some apps have had a conflict but it 
was
purly a variable/object naming issue.  Was no problem at all to create an 
instance
of both side by side as long as the obect had a different name.

IIRC phpgw's db class is a direct dirivative of phplib from a couple years ago,
which I believe is where READ comes from too, right?

Jim Foster (address@hidden) wrote*:
>
>This is a general inquiry directed mainly to the db gurus of the phpGW
>core team:
>
>I have noticed that more and more open source apps are taking advantage
>of PEAR's db abstraction layer. I would expect this trend to increase as
>developers become more standards sensitive, as well as realize the
>futility in recreating the wheel. This is to say nothing of the fact
>that the PEAR DB is being merged with the Metabase php database
>abstraction layer.
>
>When browsing an open source app there have been times that I thought
>the app I was looking at would be a good candidate to integrate with
>phpGroupWare. Problem is the conflict in phpGroupWare's db class with
>the PEAR DB class.
>
>Surely the core team has noticed this, too.
>
>Are there any plans to address this? Or is phpGW definitely staying
>proprietary?
>
>Thanks for you thoughts/feedback!
>
>Jim
>
>
>