RE: [PEAR-DEV] Re: [metabase-dev] numRows in the oracle driver

> From: Manuel Lemos [mailto:mlemos@acm.org] > Sent: Tuesday, March 11, 2003 3:22 PM > > If people want to traverse the result set more than once they can just > > do just that by using one of the bulk fetching methods. Then they have > > the data in an array with which they can do whatever they want. > > That is not the same thing. For database API like MySQL that already > does their own buffering you are making the application spend more > memory using bulk fetching. Well I don't remember how this is handled in Metabase, but in MDB/DB the result set is freed after the bulk fetching. So once the entire result set is traversed you will only have the array. > > Ah, you misunderstood me. I also want to make it possible for the > > programmer to set such a hint. Probably introducing a new option. > > I wanted to add this option before to Metabase, not because of Oracle > but since MySQL got a non-buffered query function. The problem is that > you can have more than one opened non-buffered query in MySQL, so I left > it the way it was for a while to give it more time to think of a more > realistic solution. So maybe now is the time to move? How do you feel about doing this in Metabase? > > So then we would buffer the result set if users say they want to and in > > the default not buffer. I just got a mail from Lorenzo who is working on > > Yes, but I would default to do buffering because that is the current > behaviour of MySQL and several other database API that are popular among > PHP users. Keep in mind that MySQL is most people's first database they > work with in PHP. Yeah you are right. Regards, Lukas