[Cdeengine-chat] Inital Welcome & Tasking for the Cross Database Engine Team
Uniform Database Abstraction for PHP Development
Brought to you by:
andrevanzuydam
From: Andre v. Z. <an...@sp...> - 2008-08-30 12:44:13
|
Welcome everyone, currently we're a team of 5 and here is how I propose we forward the project. I will be leading the development and help test what everyone is busy developing. Ivan Cat will be heading up the PostGres development & functionality and helping with the releases of the project Ashraf will be heading up the MySQL development & functionality Wimpie Vermaak will be doing the SQLite development & functionality Lukskywalker will be helping out on MSSQL ? To summarize: The Cross Database Engine is fairly easy to implement when it comes to adding other databases, however this is not the main aim of the project. The main aim will remain to create or interpret between the different database environments so that Developer A developing in Database B with CDE can safely run his application on Database C without changing his code and this means his SQL either. Our current areas of need are as follows: 1. The various PHP databases need to be encapsulated which is happening rather rapidly. 2. The parsesql functionality needs to be discussed and a plan must be thought out about how this can work efficiently (this translates the SQL) 3. Blob / Clob / Binary object support needs to be completed for each database environment, I've done it for Firebird but do not know how it works for the rest. 4. Each area where there is functionality lacking for a particular database it needs to be added. For instance Firebird had no support for numrows so I added it. 5. There is a new file in the CVS which is called cdetestclass.php which I'm going to add some routines to which should work on your database environments, if they do not work then there is some work to be done in the parsesql for the particular environment. (The initial database is SQLite which will port to the others) Ideas are welcome here about how to test from PostGres to Firebird etc ... 6. Date handling is quite a bother between databases, some stuff I test in SQLite works but doesn't work in Firebird & MSSQL hence the tran_date function, however I still have problems with it. 7. Use this list as a forum for sharing information as the public can use it as a reference also. And thats about it for now, lets see if we can tackle these issues and work to testing with the cdetestclass.php which will become our standard benchmark. I welcome any ideas to ensure the success of this project and remember our work needs to be good as developers will be putting their faith in our engine. Yours sincerely Andre van Zuydam |