Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
> The problem here is that you can execute as many statements as you
> want on a connection, so having all of the statements block on the
> first statement or reading all of the first statements data
> doesn't solve the problem since you could run out of memory
> reading the first statements' data.
It doesn't solve it for all cases, but it would make the default
behavior for many common usages more efficient. FWIW, it would
match the behavior of the Sybase and MS SQL Server JDBC drivers, at
least last I used them.
As I said earlier in the thread, I think we may need a new protocol
version to have a really nice implementation which completely solves
the problem. People are talking about that anyway, for a variety of
reasons, so we should make sure that if that effort moves forward
the new protocol can gracefully handle this case along with solving
the other problems people want to address.
-Kevin