Bug #43889 closing half-read resultset causes is O(n) instead of O(1)

Submitted: 26 Mar 2009 16:07 Modified: 26 Mar 2009 16:28
Reporter: yoav morag Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: General Severity:S5 (Performance)
Version:5.1 OS:Linux
Assigned to: CPU Architecture:Any

[26 Mar 2009 16:07] yoav morag 
Description:
see the following bug submitted to ConnectorJ and the team response: http://bugs.mysql.com/bug.php?id=42929

I need this functionality because not all data can be selected using where - sometime the user needs to iterate on the data and process it - however it should always be possible to close such a session immediately.

How to repeat:
see java example in : http://bugs.mysql.com/bug.php?id=42929
[26 Mar 2009 16:28] Valeriy Kravchuk 
Change in the protocol that would allow to stop reading the result set at any moment would be useful in some cases.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.050 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.