Re: [Phpgroupware-developers] XML & Schema Proc

[Michael Dean]

I still believe switching out the entire database backend is risky and
will not be as simple as replacing method calls.

- Re: maintenance: I don't have a problem maintaining the classes and am
willing to commit to do so.  I also have my own classes in DCL that
contain SQL server specific functions for things like getting the
current date/time, converting to upper case performing a rtrim, etc. 
These functions can be ported giving more flexibility and compatibility
to the layer.

- Re: porting: I don't think adodb has any advantages here.  There are
still projects that don't even use an abstraction layer.

- Support for other RDBMS:  phpLib has classes for other servers that
have not been bought into the phpGW fold yet.

On Fri, 2003-05-02 at 01:02, Lars Kneschke(priv.) wrote:
> - We don't need to maintain it. This is one important point for me. We
> really don't have the man power to add all the supported databases to our
> database class. And currently is no one developing this classes anymore.
> It would be nice to have a class which gets developed further without our
> need.
> 
> - Porting
> There are many projects which are using ADODB. These projects can be easier
> ported to phpGroupware, when we use the same database class.
> 
> - Support for more databases then we have now.
> 
> 
> 
> The only feature i see is missing, is the table creation stuff. But maybe we
> can work together with the adodb people, to get this into adodb.