andrey@lmy004.
950a277988
retest the fix for bug #10362 (SHOW PROCEDURE always qualifies name with database)
...
(already approved)
2005-08-27 12:29:36 +02:00
monty@mishka.mysql.com
aa18382680
Make test predictable
2005-08-25 12:03:19 +03:00
georg@lmy002.wdf.sap.corp
adc603a930
Merge lmy002.wdf.sap.corp:/home/georg/work/mysql/bugs/mysql-5.0-master
...
into lmy002.wdf.sap.corp:/home/georg/work/mysql/bugs/mysql-5.0_5501
2005-08-25 07:02:37 +02:00
georg@lmy002.wdf.sap.corp
254db48603
Fix for bug#5501 (SHOW TABLE STATUS should show "view" in upper case)
2005-08-24 12:51:00 +02:00
igor@rurik.mysql.com
21b63441f5
Merge rurik.mysql.com:/home/igor/mysql-5.0
...
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
2005-08-22 17:46:21 -07:00
igor@rurik.mysql.com
94166de5f3
sql_show.cc:
...
Database name was set incorrectly for any show command
that used sunqueries in its where condition.
information_schema.test, information_schema.result:
Added a test case for bug #12636 .
2005-08-22 17:32:02 -07:00
monty@mishka.local
49413542bd
Merge bk-internal.mysql.com:/home/bk/mysql-5.0
...
into mishka.local:/home/my/mysql-5.0
2005-08-22 16:06:00 +03:00
monty@mishka.local
1c1f26d5e2
Fixes during review of new pushed code
...
Fixed new bug when running a SP without a default database
2005-08-20 11:00:00 +03:00
jimw@mysql.com
dd1e0fb8c7
Merge mysql.com:/home/jimw/my/mysql-5.0-11711
...
into mysql.com:/home/jimw/my/mysql-5.0-clean
2005-08-19 11:40:39 -07:00
aivanov@mysql.com
ed6cd805dc
information_schema.test:
...
Added a comment line for a test case used for bug #12301 .
information_schema.result:
Fixed some test cases results (bug #12301 ).
sql_show.cc:
Fixed bug #12301 .
The bug was due to a missing value setting for the NUMERIC_SCALE column
in the get_schema_column_record() function (sql_show.cc).
2005-08-16 23:11:04 +04:00
acurtis@xiphis.org
c414bb1520
Bug#12518
...
"COLUMN_DEFAULT has wrong value if NOT NULL is set"
Show NULL instead of empty string when no default value is set
2005-08-15 17:14:55 +01:00
dlenev@mysql.com
0c38d33507
Merge bk-internal.mysql.com:/home/bk/mysql-5.0
...
into mysql.com:/home/dlenev/src/mysql-5.0-is
2005-08-09 11:43:55 +04:00
jimw@mysql.com
2b04134439
Report 'SYSTEM VIEW' as table_type of INFORMATION_SCHEMA views. (Bug #11711 )
2005-08-08 12:59:04 -07:00
dlenev@mysql.com
615baa9f23
Fix for bug #10055 "Using stored function with information_schema causes empty
...
result set".
To enable full access to contents of I_S tables from stored functions
or statements that use them, we manipulate with thread's open tables
state and ensure that we won't cause deadlock when we open tables by
ignoring flushes and name-locks.
Building of contents of I_S.TABLES no longer requires locking of tables
since we use use handler::info() method with HA_STATUS_AUTO flag instead
of handler::update_auto_increment() for obtaining information about
auto-increment values. But this also means that handlers have to implement
support for HA_STATUS_AUTO flag (particularly InnoDB needs it).
2005-08-08 17:46:06 +04:00
andrey@lmy004.
3a52916436
fix for bug #12315 - SHOW TABLE STATUS FROM information_schema
; does not sort tablenames
2005-08-05 11:01:29 +02:00
jimw@mysql.com
6557fca0bd
Update out-of-date test result
2005-08-02 18:27:05 -07:00
jimw@mysql.com
698f209917
Fix test to avoid spurious failure message. (Bug #11233 )
2005-08-02 16:50:10 -07:00
bell@sanja.is.com.ua
4a0d64af89
Merge sanja.is.com.ua:/home/bell/mysql/bk/mysql-5.0
...
into sanja.is.com.ua:/home/bell/mysql/bk/work-trigger-5.0
2005-07-29 23:43:07 +03:00
bell@sanja.is.com.ua
b220fc47ef
store/restore sql_mode which was in force during ctrigger creation (BUG#5891)
...
other sql_mode fixes
2005-07-28 22:39:11 +03:00
gluh@eagle.intranet.mysql.r18.ru
ef2c7812f3
Fix for bug#12127 triggers do not show in info_schema before they are used if set to the database(2nd version)
...
use db name of table which trigger belongs to
instead of thd->db name during trigger body parsing
2005-07-27 16:17:05 +05:00
gluh@eagle.intranet.mysql.r18.ru
c1c504abf4
merge fix
2005-07-21 18:43:55 +05:00
dlenev@mysql.com
b141437ad3
Merge bk-internal.mysql.com:/home/bk/mysql-5.0
...
into mysql.com:/home/dlenev/src/mysql-5.0-tn
2005-07-19 20:55:09 +04:00
dlenev@mysql.com
8a3e723b74
Fix for bugs #5892/6182/8751/8758/10994 (based on Antony's patch)
...
"Triggers have the wrong namespace"
"Triggers: duplicate names allowed"
"Triggers: CREATE TRIGGER does not accept fully qualified names"
"SHOW TRIGGERS"
2005-07-19 20:06:49 +04:00
gluh@eagle.intranet.mysql.r18.ru
d1bc1b7c0e
Fix for bug#11057 information_schema: columns table has some questionable contents
...
fixed BLOB, TEXT(wrong maximum length), BIT and integer types(wrong numeric_precision value)
2005-07-19 14:30:32 +05:00
gluh@eagle.intranet.mysql.r18.ru
d59ff2764c
Bug#11577 'show procedure/function status' doesn't work for user with limited access
...
changed 'SHOW PROCEDURE' behavoiur to be like INFORMATION_SCHEMA.routines
2005-07-19 13:49:43 +05:00
gluh@eagle.intranet.mysql.r18.ru
9c3349f5c6
Fix for bug#11685 SHOW TABLES; doesn't update Com_show_tables
2005-07-13 13:30:39 +05:00
jimw@mysql.com
a2244a9094
Merge jwinstead@production.mysql.com:my/mysql-5.0-10844
...
into mysql.com:/home/jimw/my/mysql-5.0-clean
2005-07-05 15:24:35 -07:00
monty@mysql.com
ec420bfb43
Fixes during review of new code
...
- Mostly indentation fixes
- Added missing test
- Ensure that Item_func_case() checks for stack overruns
- Use real_item() instead of (Item_ref*) item
- Fixed wrong error handling
2005-07-04 03:42:33 +03:00
jimw@mysql.com
01c690b79b
Fix information_schema test on Windows. (Bug #10844 )
2005-06-18 03:02:27 +02:00
gluh@eagle.intranet.mysql.r18.ru
c7dde629b7
Fix for bug#9434 SHOW CREATE DATABASE information_schema
;
...
added ability to do SHOW CREATE DATABASE `information_schema`
2005-06-16 13:27:22 +05:00
gluh@eagle.intranet.mysql.r18.ru
a851311d77
Fix for bug#11055: information_schema: routines.sql_data_access has wrong value
2005-06-16 12:12:47 +05:00
gluh@mysql.com
ac76e6db6a
Merge sgluhov@bk-internal.mysql.com:/home/bk/mysql-5.0
...
into mysql.com:/home/gluh/MySQL/Bugs/5.0.10964
2005-06-07 11:31:07 +05:00
gluh@eagle.intranet.mysql.r18.ru
477feba00f
Fix for bug#10964: Information Schema:Authorization check on(2nd version, after review)
...
privilege tables is improper
added privilege check for USER_PRIVILEGES, SCHEMA_PRIVILEGES,
TABLE_PRIVILEGES, COLUMN_PRIVILEGES tables
2005-06-02 15:33:53 +05:00
monty@mysql.com
a69f432115
Code cleanups during code reviews
...
Ensure we get error if INSERT IGNORE ... SELECT fails
Fixed wrong key_part->key_length usage in index_merge
2005-06-01 16:35:09 +03:00
gluh@eagle.intranet.mysql.r18.ru
ddf91f0689
Fix for bug#10059: SHOW TABLE STATUS FROM information_schema
; reports uppercase table names
...
information schema table names are always upper case table names
2005-05-31 13:15:23 +05:00
gluh@gluh.mysql.r18.ru
68317fcb0c
addition of "REFERENCED_TABLE_SCHEMA",
...
"REFERENCED_TABLE_NAME", "REFERENCED_COLUMN_NAME" fields into
KEY_COLUMN_USAGE table
2005-05-20 16:39:28 +04:00
gluh@mysql.com
828237909f
after merge fix
2005-05-09 18:18:59 +00:00
gluh@mysql.com
03234c48cf
manual merge
2005-05-09 17:21:44 +00:00
gluh@mysql.com
12085567de
Fix for bug #9404 : information_schema: Weird error messages with SELECT SUM() ... GROUP BY queries
2005-05-09 16:22:49 +00:00
gluh@mysql.com
f6bf2680b2
Fix for bug#10261: INFORMATION_SCHEMA.COLUMNS, incomplete result for non root user
...
I_S table columns information is available for any user
2005-05-07 15:14:34 +00:00
gluh@mysql.com
64cbbf1463
Fix for bug #9838 : INFORMATION_SCHEMA.COLUMNS columns of granted views missing
2005-05-07 13:55:46 +00:00
gluh@mysql.com
f285b4fcee
Fix for bug#8998: information_schema: Table SCHEMATA should report default collations
...
DEFAULT_COLLTION_NAME field is added to SCHEMATA table
2005-05-06 20:14:22 +00:00
igor@rurik.mysql.com
b622aba19f
information_schema.result, information_schema.test:
...
Added a test in connection with the fix for
bug #6106 .
view.result, view.test:
Added test cases for bugs #6106/6107.
sql_show.cc:
The addition of the case for items of the type REF_ITEM in the
function uses_only_table_name_fields became necessary after
the fix for bug #6106 .
sql_base.cc:
The problem was due to the fact that two different column
references were glued together though one of them belonged to
a subquery while another to an outer query. This caused
eventually a wrong calculation of values for the used_tables
attribute.
2005-04-13 23:06:37 -07:00
gluh@eagle.intranet.mysql.r18.ru
6c8c2d22b9
Fix for bug#7214: information_schema: unauthorized user can see metadata
...
the fix for 'columns' table only
Rights check for 'routines' table is already done
(see WL2131 Access control for SHOW ... PROCEDURE|FUNCTION ...)
rename 'testtets' database to 'mysqltest' to keep number of
DBs which created by mysql-test as small as possible
2005-04-05 15:12:15 +05:00
gluh@eagle.intranet.mysql.r18.ru
1f38b5bdd1
Fix for bug #9344 INFORMATION_SCHEMA, wrong content, numeric columns
...
The columns CHARACTER_MAXIMUM_LENGTH and CHARACTER_OCTET_LENGTH
of INFORMATION_SCHEMA.COLUMNS must be NULL for numeric columns
2005-03-31 13:44:42 +05:00
gluh@gluh.mysql.r18.ru
fe0b425e0a
Merge sgluhov@bk-internal.mysql.com:/home/bk/mysql-5.0
...
into gluh.mysql.r18.ru:/home/gluh/MySQL-BUGS/mysql-5.0.8941
2005-03-25 15:09:22 +03:00
gluh@gluh.mysql.r18.ru
d5e448870d
Fix for bug #8941 : garbage MAX_ROWS=# from SHOW CREATE TABLE INFORMATION_SCHEMA.*
...
-skip the print of 'MAX_ROWS=#' for 'SHOW CRETAE TABLE' with information schema tables
2005-03-25 12:19:11 +03:00
gluh@gluh.mysql.r18.ru
6ec480910d
Bug #9317 : Wrong count for tables in INFORMATION_SCHEMA
...
there was no check of result of
table->file->write_row() function. When count of rows was
more than table max_rows(HEAP table) the following recodrs
were not inserted to the table
-'schema_table_store_record' function is added.
The function checks result of write_row function
and convert HEAP table to MyISAM if necessary
- Result check after write_row is added into all
I_S function which store the records to I_S tables
2005-03-24 16:32:11 +03:00
monty@mysql.com
cc56005130
Hack to ensure that CHAR's created in 5.0 are not converted to VARCHAR even if the row type is dynamic
...
(For 4.1 tables old 'VARCHAR' fields are converted to true VARCHAR in the next ALTER TABLE)
This ensures that one can use MySQL 5.0 privilege tables with MySQL 4.1
2005-03-22 15:48:06 +02:00
gluh@gluh.mysql.r18.ru
fcd50af3c7
Fix for bug #8790:Test 'information_schema': 'Max_data_length' shows 10 * (2 giga - 1) + 9
2005-03-15 20:54:44 +03:00