On Fri, 4 Jan 2002 [EMAIL PROTECTED] wrote:
> Hello, > > If everybody had _read_ Zak's initial proposal, they should have noticed > that he wanted to ADD an OO interface: > > Create an OO-based wrapper for the MySQL extension. > > Then there would would not have been an useless and endless thread. > My guess that everybody can do more useful things with their time. > Well, you might have the opinion that this an useless thread, but I don't agree. Lukas was very right in saying that the API's would get even more different if this OOP form be added. We will have 2 ways of doing the same thing in MySQL, another set of ways to do the same thing in PostgreSQL (even being similar, there are differences), another completely different way of doing things in OCI and so on. We are talking about keeping the API's as close to each other as possible. One of the things that I like in the Python development is how it is well organized - an official database API exists and module developers stick to it. It doesn't stop just on the DB API, but everywhere on its standard library and built-in functions. Please don't tell me that Python is not PHP - I know that. I just wish things were a little bit more sane in relation to standard APIs across the board. It seems that everywhere people are afraid of trying to set standards, like on the case of PEAR standards or on this case the database related API standard. Don't get me wrong, I don't have any illusion that this will change any time soon (if ever). It is still important to talk about this, and it is definetely not a useless thread to me. Joao > Derick > > > On Fri, 4 Jan 2002, Lukas Smith wrote: > > > The important thing is to keep at least the same level of functionality > > for procedural coding > > > > This was the entire concern raised about too much OOP form what I > > gather. > > > > There was also the concern raised that your design will be heavily > > influenced by the possibilities offered by the ZE1, where as the ZE2 > > will allow many new things that will result in a very different design. > > > > Also I do not like how different the API's are in some respects as it > > is. Further diverging them is nit helping imho. People that want an OOP > > interface can choose one of the major DB abstraction layers (PEAR DB, > > Metabase, ADODB ...). > > > > Then again Zak's proposal is not about abstraction but about giving an > > OOP interface and if you are going to do it anyways I guess we can > > postpone the discussion until the code is there :-) > > > > Best regards, > > Lukas Smith > > [EMAIL PROTECTED] > > _______________________________ > > DybNet Internet Solutions GbR > > Alt Moabit 89 > > 10559 Berlin > > Germany > > Tel. : +49 30 83 22 50 00 > > Fax : +49 30 83 22 50 07 > > www.dybnet.de [EMAIL PROTECTED] > > _______________________________ > > > > > > > > -- > > PHP Development Mailing List <http://www.php.net/> > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > To contact the list administrators, e-mail: [EMAIL PROTECTED] > > > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > To contact the list administrators, e-mail: [EMAIL PROTECTED] > -- Joćo Prado Maia <[EMAIL PROTECTED]> http://phpbrasil.com - php com um jeitinho brasileiro -- Precisando de consultoria em desenvolvimento para a Internet ? Impleo.net - http://impleo.net/?lang=br -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
