#At file:///misc/mysql/forest/43254_/mysql-5.0-bugteam/ based on revid:joro@stripped
2741 Tatiana A. Nurnberg 2009-03-23
Bug#43254: SQL_SELECT_LIMIT=0 crashes command line client
When asking what database is selected, client expected
to *always* get an answer from the server.
We now handle failure more gracefully.
See comments in ticket for a discussion of what happens,
and how things interlock.
@ client/mysql.cc
Handle empty result-sets gracefully, as opposed
to just result sets with n>0 items that may themselves
be empty.
modified:
client/mysql.cc
=== modified file 'client/mysql.cc'
--- a/client/mysql.cc 2009-02-10 12:39:14 +0000
+++ b/client/mysql.cc 2009-03-23 04:08:32 +0000
@@ -2625,7 +2625,7 @@ static void get_current_db()
(res= mysql_use_result(&mysql)))
{
MYSQL_ROW row= mysql_fetch_row(res);
- if (row[0])
+ if (row && row[0])
current_db= my_strdup(row[0], MYF(MY_WME));
mysql_free_result(res);
}
Attachment: [text/bzr-bundle] bzr/azundris@mysql.com-20090323040832-xd0li3ji1zse0o0z.bundle
| Thread |
|---|
| • bzr commit into mysql-5.0-bugteam branch (azundris:2741) Bug#43254 | Tatiana A. Nurnberg | 23 Mar |