Bug #24048 Option to keep session (connection) open after query
Submitted: 7 Nov 2006 16:19 Modified: 11 Mar 2009 11:31
Reporter: Yahoo Serious (Silver Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S4 (Feature request)
Version:1.2.4 beta OS:Any (all?)
Assigned to: CPU Architecture:Any

[7 Nov 2006 16:19] Yahoo Serious
Description:
It would be very handy to (have an option to) keep the session (connection) open after a query. 

This way it is possible to use (among others?):
- use SHOW ERRORS and SHOW WARNINGS
- use LAST_INSERT_ID() and @@IDENTITY commands (Bug #10763)
- use SET CHARACTER SET (part of Bug #6982) 
- use manual START TRANSACTION (Bug #18045)
I (and I think a lot of people) test their SQL first using QB before implementing it.  It would be nice to be able to also test these session-dependent features.

I gather from (Bug #6982) the reason this is not used at this moment is to allow:
- parallel execution of selects that take a long time or return a lot of data.
- stopping execution of a query while fetching rows without client side cursors.

But if we make it a non-default option (per query, per tab, per connection, or per user), both will be possible.

How to repeat:
feature request

Suggested fix:
feature request
[7 Nov 2006 18:09] MySQL Verification Team
Thank you for the bug report, feature request.
[13 Nov 2006 16:05] Yahoo Serious
This is also needed for:
 - FOUND_ROWS()
 - ROW_COUNT()
[12 Dec 2006 11:36] Yahoo Serious
Also needed for EXPLAIN EXTENDED (see Bug #22576)
[11 Mar 2009 11:31] Susanne Ebrecht
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at

  http://www.mysql.com/downloads/