Re: Proposed updates and extensions to the MySQL extension

On Thu, 3 Jan 2002, Zak Greant wrote: > On 2002-3-01 03:39, Lukas Smith wrote: > > Well PHP and MySQL are a very popular combo .. but I do not see a point > > in "separating" the API's even further ... DB API's are a major > > concern > > for myself right now too > > > > It would be really nice to work more in the direction of unifying all of > > the API's on a "C level" > > > > Other than that there is nothing against doing that change .. but I > > think it would only make sense to do it across the board > > I plan to keep my focus on this very small to avoid distraction. :) > > I am currently working on a PHP based implementation that uses Andrei's > overload extension. Once I this is somewhat stable and users have had a > chance to work with it, I plan to implement it in C. > My personal opinion is that the OOP layer idea is pretty bad. Instead of having 7 or 8 set of functions to learn, now the newbie will have 8 set of functions / APIs. The idea might sound very sexy and everything, but the real problem is that there is already _some_ talks in PEAR-DEV about trying to create a unified API for all databases (a new one, not PEAR::DB) which would be eventually be ported to C. I really don't feel very good with yet another database abstraction package, and this time just for MySQL. I say database abstraction not in the sense that it will abstract everything, but that it gives a thin layer of abstraction to the underlying database. In any case, I _really_ hope you will talk with Stig and get to know more about the latest discussions (flame-wars?) in PEAR-DEV about the upcoming re-write of PEAR::DB and also about the intention of re-writing it in C once it is stable. Joao -- João Prado Maia <jpm@phpbrasil.com> http://phpbrasil.com - php com um jeitinho brasileiro -- Precisando de consultoria em desenvolvimento para a Internet ? Impleo.net - http://impleo.net/?lang=br