diff options
author | unknown <jimw@rama.(none)> | 2006-07-21 20:29:25 -0700 |
---|---|---|
committer | unknown <jimw@rama.(none)> | 2006-07-21 20:29:25 -0700 |
commit | da0d9f37c4b163a8dc0d8d919ee30cc5d8f58bf9 (patch) | |
tree | 9d40d89ba22d11e7092d8c13324a1d4be7fab53e /mysql-test/r/func_gconcat.result | |
parent | dc50ce997083b4f3d3e4ab237c6a1f5e11cfd90f (diff) | |
download | mariadb-git-da0d9f37c4b163a8dc0d8d919ee30cc5d8f58bf9.tar.gz |
Bug #19147: mysqlshow INFORMATION_SCHEMA does not work
When a wildcard database name is given the mysqlshow, but that wildcard
matches one database *exactly* (it contains the wildcard character), we
list the contents of that database instead of just listing the database
name as matching the wildcard. Probably the most common instance of users
encountering this behavior would be with "mysqlshow information_schema".
client/mysqlshow.c:
Add special handling for listing a single database that has a name that
looked like it contained wildcards. In this case, we just go ahead and list
the contents of the database, since there is a very high probability that is
what the user really wanted to do. (For example, 'mysqlshow INFORMATION_SCHEMA'
will show the I_S tables instead of just the I_S database.)
mysql-test/r/mysqlshow.result:
Add new results
mysql-test/t/mysqlshow.test:
Add new regression test
Diffstat (limited to 'mysql-test/r/func_gconcat.result')
0 files changed, 0 insertions, 0 deletions