Looking at other aspects of the Sql module I think it might be an idea to dispose of the wrapper. Instead of having Sql.Sql wrap Sql.* that inherits C-code, we could have the C-modules inherit Sql.DB and then let Sql.open create the actual objects (from Sql.* programs). That way we can access database specific functions directly and remove one level of indirection when calling API functions. Since the access API is a new one, we can redesign whatever we want...
/ Martin Nilsson (DivX Networks)
Previous text:
2004-10-13 23:02: Subject: Re: MySQL big_query in 7.7
But I still think that it is feasible to make big_query() intelligent and pull in the rest of the stream, as soon as it notices another big_query() being started on the same connection.
I was hoping Per would respond to this, since he's the one who's having trouble with it. Anyway, as far as I've understood that might not be good enough since it can keep the tables locked for too long. I.e. it can be important that the whole response is read quickly if there are other users of the database. And having a pike loop that reads it all in before it's used would create the same kind of bulky pike structures that query() suffers from.
/ Martin Stjernholm, Roxen IS