mysql-python loses anything past the first message

[sam-leonard-ct]

Describe the bug

mssql-python doesn't return anything after the first message

To reproduce

This is the minimum test case I could get to reproduce the bug, this script passes when cursor is from pyodbc, but not when cursor is from mysql-python.

cursor.execute("""
PRINT('hi');
PRINT('ih');
""")

assert cursor.messages == [('[01000] (0)', '[Microsoft][ODBC Driver 18 for SQL Server][SQL Server]hi')]

assert cursor.nextset()
# on mysql-python this second message is missing
assert cursor.messages == [('[01000] (0)', '[Microsoft][ODBC Driver 18 for SQL Server][SQL Server]ih')]

assert not cursor.nextset()

Expected behavior

All messages from the operation should be returned via cursor.messages at some point before cursor.nextset() returns False, preferably in the order detailed in the above script.

Further technical details

Python version: 3.12.11
SQL Server version: SQL SERVER 2017
Operating system: macOS 26.5

[github-actions]

Hi @sam-leonard-ct, thank you for opening this issue!

Our team will review it shortly. We aim to triage all new issues within 24-48 hours and get back to you.

If you have additional information to share, please feel free to update the issue.

Thank you for your patience!

[jahnvi480]

Thanks for the detailed report and repro, @sam-leonard-ct!

We've triaged this and confirmed it's a bug. The root cause is that cursor.nextset() calls SQLMoreResults under the hood but doesn't check for SQL_SUCCESS_WITH_INFO to capture diagnostic messages (like PRINT output). The first PRINT is captured correctly by execute(), but any subsequent messages delivered via SQLMoreResults were silently dropped.

We'll have a PR up shortly with the fix.

[sam-leonard-ct]

Thanks for the detailed report and repro, @sam-leonard-ct!

We've triaged this and confirmed it's a bug. The root cause is that cursor.nextset() calls SQLMoreResults under the hood but doesn't check for SQL_SUCCESS_WITH_INFO to capture diagnostic messages (like PRINT output). The first PRINT is captured correctly by execute(), but any subsequent messages delivered via SQLMoreResults were silently dropped.

We'll have a PR up shortly with the fix.

Awesome, thanks for the quick debugging!