Re: Are there Sql backends that return an array from big_query()?

> 
> Well, actually, the only real incompatibility would be reference to master_sql
> which is not needed anymore.  But it's easy to still keep
> it around for real or in compat using a plain reference to "this".

That would be helpful.  . I do agree with the overall working concept, but don't relish having to sift through 20 years of code. :)

> 8.1, there is no need to commit it to 8.0.  It's merely a code cleanup
> which results in better structure, less overhead and slightly enhanced
> speed (contrary to the new pgsql driver, which fixes real bugs in the
> old one, so I intend to backport it to 8.0 once stabilised).

Ok, was just curious. 

> 
> Well, as it seems, Sql.Sql()->big_query(), accepts sprintf like
> arguments.  The real backend's big_query() only accepts bindings
> (usually), so there is going to be some minimal wrapping anyway,
> which (in turn) means that I can still accomodate for the array
> return object as well.  It also means that I'll provide for some
> kind of "raw_query()" method which calls the underlying backend
> big_query() without wrapping.

I that's a minor, but nice point.

Thanks for the clarification!

Bill