Skip to content

Commit 59e11ee

Browse files
gkodinovdahlerlend
authored andcommitted
Bug #32955044: SELECT QUERY RETURNING 0 ROWS DESPITE TABLE CONTAINING DATA
RB#26560 Updated the release version in the check to account for the extra release
1 parent 49e9dc6 commit 59e11ee

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

libmysql/libmysql.cc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1761,7 +1761,7 @@ static bool execute(MYSQL_STMT *stmt, char *packet, ulong length,
17611761
If the server supports query attributes raise the flag that we
17621762
are going to be sending the parameter block.
17631763
Unfortunately there's a bug in processing the flags in servers
1764-
earlier than 8.0.25 that conflates all the flags into a single
1764+
earlier than 8.0.26 that conflates all the flags into a single
17651765
boolean. Thus we need to cut off sending PARAMETER_COUNT_AVAILABLE
17661766
for these
17671767
*/
@@ -1851,7 +1851,7 @@ int cli_stmt_execute(MYSQL_STMT *stmt) {
18511851
bool send_named_params =
18521852
(mysql->server_capabilities & CLIENT_QUERY_ATTRIBUTES) != 0;
18531853
bool can_deal_with_flags =
1854-
mysql->server_version && mysql_get_server_version(mysql) >= 80025;
1854+
mysql->server_version && mysql_get_server_version(mysql) >= 80026;
18551855
/*
18561856
When the server can deal with flags properly we should send the 0 param
18571857
count even when there's no parameters when the server supports named

0 commit comments

Comments
 (0)