Re: Adoption of Metabase (was Re: [PEAR-DEV]Re:Comparing ADODB with PEAR DB, Metabase andNative MySQL)

On Tue, 2001-11-20 at 08:41, Manuel Lemos wrote: > Hello, > > doesn't scale (try inserting 2GB data in MySQL). As for Oracle you have > to insert and empty LOB to make it work. PEAR-DB does not do it. It just > uses bind variables which is good for upto 4Kb VARCHAR fields. Those are > not large object fields. > OK you got me there :) This can be easily implemented though, but the need has not arisen, in fact AFAIK the only one who has ever asked for such a feature in this list was me :) > > > I have just talked about this meta-language in Frankfurt's PHP > Conference just a couple of weeks ago. The database procedure > meta-language will not be ready soon, but you may find more the whole > meta-language thing here: http://www.meta-language.net/ . > I'll check it out, bit I think trying to develop a common stored procedure language is like trying to develop a unified programming language (read people will alway use their thing.) > > > What is so complicated about it? Maybe it just does more than you need? > Just don't use what you don't need. > You've misunderstood me if you can show me a way to do this in metabase in two lines of code, I'll reconsider <?php $db = DB::connect("somedsn"); $data = $db->getAll("some query"); //process data ?> > > > > Standards will only be standards when everbody agrees with them. They > way PEAR standards were pushed a lot of people will simply disagree and > will not adhere. Leaving out people this way the community will not > grow. > I agree but you should add to that that once standards have been agreed on and used for a couple of years, you don't just change them because new people come up with arguments i don't like them or sturdy caps make my eyes weep. > > > > > > > > I don't have the time. My point is that if Stig is willing to spend a > > > year or whatever it takes to port PEAR-DB to C, why not porting Metabase > > > API instead and benefit from all those points that I mentioned? > > > > > > > So basically you need some one to do the work for you in the true spirit of > > Absolutely not. It is not really very important for me the port to C. It > will take a long time until it would become useful. Believing otherwise > is wishful thinking. There are a lot of projects in the Open Source > world that fail because of that. People think that just because they > can, they will do it. When they realize it will be taking too long they > give up. > > My most important point is end with just one database abstraction > package to let PHP developers write database independent applications, > just like other people do with other languages. It is silly that PHP is > different. > And you want that to be metabase, but just as you will not be willing to drop metabase for some other db abstaraction, the same goes for PEAR::db developer or ADBDB or any other project. > > > cooperation. I don't mean to be harsh but if you want to cooperate try integrating > > I don't have the time or motivation to develop things for PEAR just > because it is funny to cooperate. I am no longer a college student so I > don't have plenty of free time to spare. What I do is because I need the > things for my job. If I am not selling what I do, I don't have a problem > with sharing. That is what I am doing with Metabase. > > One thing is certain, I don't want to go where I am not wanted. If there > is no interest in integrating Metabase in PEAR, fine. If not, I don't > have a problem with that. From the silence of PEAR core developers, I am > afraid there isn't much hope from their side to cooperate. At least I > made an honest attempt to cooperate. > Being unwanted is not the issue here the point is that the only proposition you made was someone else to port metabase to C for you in the spirit of true cooperation I find that a bit hypocritic, of course I cannot answer that because the question was not addressed to me. > > > > these better features into PEAR. But I'm sure that this is not what you have in mind > > because you think that met abase is much better, and you might be right, but when you come > > in a spirit of cooperation you must offer something and not expect to get something in > > return. > > So don't get me wrong but what exactly are you offering. > > Maybe you need to know better Metabase to realize what I am giving away. > It's about 3 years of development on something that there is nothing > like that neither for PHP nor for any other language, a database > abstraction that not only provides independence to database access but > also to database schema installation and maintence. The details you may > find about in the manual and the tutorials available from the PHP > Classes site. > Maybe I was not clear, here. What do you offer than what is already there. I do not mean to belitle your work I sure metabase is a good thing but still the question remains. yavo