Bug #61568 Result is not grouped on sequential store procedure runs
Submitted: 20 Jun 2011 14:22 Modified: 21 Jun 2011 6:40
Reporter: Mikhail Sedov Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Stored Routines Severity:S2 (Serious)
Version:5.5.15, 5.5.13 OS:Any
Assigned to: CPU Architecture:Any
Tags: GROUP BY, query, stored procedure
Triage: Needs Triage: D2 (Serious)

File: Maximum allowed size is 3MB.

If the data you need to attach is more than 3MB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (recommended filename: mysql-bug-data-61568.zip) and upload one to sftp.oracle.com. A free Oracle Web (SSO) account (the one you use to login bugs.mysql.com) and a client that supports SFTP are required in order to access the SFTP server.

To upload the file to sftp.oracle.com:

  1. Open an SFTP client and connect to sftp.oracle.com. Specify port 2021 and remote directory /support/incoming/.
  2. Log in with your newly created Oracle Web account (email address) and password.
  3. Upload the archive to /support/incoming.
  4. Once you have uploaded the file, add a comment to this bug to notify us about it.
Example: sftp -oPort=2021 -oUser=email sftp.oracle.com:/support/incoming

Usage Notes: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it. A file cannot be uploaded more than once with the same filename. The filename must be changed before attempting to upload the file again. The filename should always start with mysql-bug- prefix. Files are retained on the SFTP server for 7 days and then permanently removed.

[20 Jun 2011 14:23] Mikhail Sedov
script to reproduce the problem

Attachment: db_issue.sql (application/octet-stream, text), 4.35 KiB.

[20 Jun 2011 14:23] Mikhail Sedov
possible workaround

Attachment: db_issue_workaround.sql (application/octet-stream, text), 4.42 KiB.