Not sure why you'd want to compare those. ADODB doesn't have DDL
support (only has alpha quality table/index creation) and the Metabase
portion of MDB that does support DDL would be either risky to run or
require much more overhead to ensure the risk is eliminated. Metabase
was considered for phpGW once already, but examination of the code
proved it would not be suitable.
To boot, you incur a LOT of risk switching APIs. Even if you have a
wrapper to introduce interface compatibility because the implementations
are going to be very different. Wrappers also incur their own overhead
because of their nature.
I don't see a reason to replace the database classes, but perhaps you
can share the concerns? Between the classes and schema proc, you have
total control over the database and setup/upgrade processes. The other
packages don't come close.
On Thu, 2003-05-01 at 09:34, Chris Weiss wrote:
how would this compair to using ADODB or one of the PEAR based projects?
Michael Dean (address@hidden) wrote:
Hey all!
In talking to skwashd about doing some schema proc work, I brought up
the fact that I have an XML definition for defining the database schema
that is used by DCL HEAD and GNU Enterprise. What I'd like is to get a
feel for the level of interest in moving schema proc to run completely
from XML.
I currently have style sheets that perform the following:
* Create MSSQL XML command script
* Create MySQL XML command script
* Create PostgreSQL XML command script
* Create Sybase XML command script
* Transform a command script into a SQL script
* Transform the original definition into a DHTML schema browser
The XML command script mentioned above is just a series of SQL
statements that can be ran.
What this definition lacks is defining default data and upgrades. It
should also be noted that a transform could be created to generate PHP
if one was so inclined.
I feel with the move to XML/XSLT in phpGW that this is a very logical
step to take. It also makes supporting new RDBMS' a cake on the schema
side because you just write a new transform to translate data types and
such for that particular RDBMS.
I plan on throwing this into the wiki (with more detail) if y'all would
like to make a go of it.
Mike
_______________________________________________
Phpgroupware-developers mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
_______________________________________________
Phpgroupware-developers mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
_______________________________________________
Phpgroupware-developers mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/phpgroupware-developers