2005/10/5, Sean Mollet <[EMAIL PROTECTED]>: > I sincerely appreciate any input on this. I'm going to try this shim on > my development installation and hopefully produce some benchmarks. If > the new interface really is as fast as they say it is, I suspect there > are gains to be had even with the added overhead.
Unfortunately I'm not a PHP expert so my feedback might be of limited use. Anyway, since this limitation (max 1 open result set per connection) exists for other databases as well (namely MS SQL Server) it seems to be a good strategy to generally avoid more than one open result set per DB connection. In situations where this is not directly feasible because a too large dataset has to be kept in mem any of these might help: join, stored procedure. AFAIK MS SQL Server JDBC drivers implement the same strategy as you, i.e. they uise the connection as proxy to n actual DB connections. If you get most out of this you should plan to pool those connections in order to minimize connect latencies. Kind regards robert -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
