An error occurred fetching the project authors.
- 04 Oct, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
added check for hidden I_S tables for 'show columns|keys' commands
-
- 28 Sep, 2007 2 commits
-
-
gluh@mysql.com/eagle.(none) authored
skip the check of directory presence for 'information_schema' name
-
gluh@mysql.com/eagle.(none) authored
view_body_utf8 attribute type is changed to 'escaped string'
-
- 20 Sep, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
added get_field_default_value() function which obtains default value from the field (used in store_create_info() & get_schema_column_record() functions)
-
- 21 Aug, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
added TRIGGER_ACL check for I_S.TRIGGERS
-
- 20 Aug, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
added SUPER_ACL check for I_S.TRIGGERS
-
- 09 Aug, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
1. added check to fill_schema_schemata() func. if we have db lookup value we should check that db exists 2. added check to get_all_tables() func if we have lookup db name or tables name values we shoud check that these values are not empty strings 3. fixed typo
-
- 02 Aug, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
-
- 11 Jul, 2007 1 commit
-
-
kostja@bodhi.(none) authored
Fix the parser to make the database options not optional.
-
- 28 Jun, 2007 1 commit
-
-
anozdrin/alik@ibm. authored
- BUG#11986: Stored routines and triggers can fail if the code has a non-ascii symbol - BUG#16291: mysqldump corrupts string-constants with non-ascii-chars - BUG#19443: INFORMATION_SCHEMA does not support charsets properly - BUG#21249: Character set of SP-var can be ignored - BUG#25212: Character set of string constant is ignored (stored routines) - BUG#25221: Character set of string constant is ignored (triggers) There were a few general problems that caused these bugs: 1. Character set information of the original (definition) query for views, triggers, stored routines and events was lost. 2. mysqldump output query in client character set, which can be inappropriate to encode definition-query. 3. INFORMATION_SCHEMA used strings with mixed encodings to display object definition; 1. No query-definition-character set. In order to compile query into execution code, some extra data (such as environment variables or the database character set) is used. The problem here was that this context was not preserved. So, on the next load it can differ from the original one, thus the result will be different. The context contains the following data: - client character set; - connection collation (character set and collation); - collation of the owner database; The fix is to store this context and use it each time we parse (compile) and execute the object (stored routine, trigger, ...). 2. Wrong mysqldump-output. The original query can contain several encodings (by means of character set introducers). The problem here was that we tried to convert original query to the mysqldump-client character set. Moreover, we stored queries in different character sets for different objects (views, for one, used UTF8, triggers used original character set). The solution is - to store definition queries in the original character set; - to change SHOW CREATE statement to output definition query in the binary character set (i.e. without any conversion); - introduce SHOW CREATE TRIGGER statement; - to dump special statements to switch the context to the original one before dumping and restore it afterwards. Note, in order to preserve the database collation at the creation time, additional ALTER DATABASE might be used (to temporary switch the database collation back to the original value). In this case, ALTER DATABASE privilege will be required. This is a backward-incompatible change. 3. INFORMATION_SCHEMA showed non-UTF8 strings The fix is to generate UTF8-query during the parsing, store it in the object and show it in the INFORMATION_SCHEMA. Basically, the idea is to create a copy of the original query convert it to UTF8. Character set introducers are removed and all text literals are converted to UTF8. This UTF8 query is intended to provide user-readable output. It must not be used to recreate the object. Specialized SHOW CREATE statements should be used for this. The reason for this limitation is the following: the original query can contain symbols from several character sets (by means of character set introducers). Example: - original query: CREATE VIEW v1 AS SELECT _cp1251 'Hello' AS c1; - UTF8 query (for INFORMATION_SCHEMA): CREATE VIEW v1 AS SELECT 'Hello' AS c1;
-
- 09 Jun, 2007 2 commits
-
-
gluh@mysql.com/eagle.(none) authored
IS_UPDATABLE flag is set to 'yes' when the view has at least one updatable column and the algorithm is not 'temporary'.
-
gluh@mysql.com/eagle.(none) authored
-
- 29 May, 2007 1 commit
-
-
gkodinov/kgeorge@macbook.gmz authored
- Renamed "Using join cache" to "Using join buffer". - "Using join buffer" is now printed on the last table that "reads" from the join buffer cache.
-
- 15 May, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
-
- 04 May, 2007 1 commit
-
-
gkodinov/kgeorge@magare.gmz authored
- added join cache indication in EXPLAIN (Extra column). - prefer filesort over full scan over index for ORDER BY (because it's faster). - when switching from REF to RANGE because RANGE uses longer key turn off sort on the head table only as the resulting RANGE access is a candidate for join cache and we don't want to disable it by sorting on the first table only.
-
- 05 Apr, 2007 1 commit
-
-
kostja@vajra.(none) authored
Apparently it's the only platform in pushbuild where we compile without openssl.
-
- 04 Apr, 2007 1 commit
-
-
kostja@vajra.(none) authored
-
- 03 Apr, 2007 1 commit
-
-
kostja@bodhi.local authored
-
- 02 Apr, 2007 1 commit
-
-
Kristofer.Pettersson@naruto. authored
- Some variables in I_S.GLOBAL_STATUS were depending on a network connection in order to evaluate. Since no network connection is present during the execution of an event, this caused the server to crash. - The variable function hooks does now verify that the vio- object is valid before attempting to use it.
-
- 27 Mar, 2007 1 commit
-
-
iggy@recycle.(none) authored
- mysqldump executes a SHOW CREATE VIEW statement to generate the text that it outputs. When the function name is retrieved it's database name is unconditionally prepended. This change causes the function's database name to be prepended only when it was used to define the function.
-
- 13 Feb, 2007 1 commit
-
-
igor@olga.mysql.com authored
-
- 12 Feb, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
The crash happens because second filling of the same I_S table happens in case of subselect with order by. table->sort.io_cache previously allocated in create_sort_index() is deleted during second filling (function get_schema_tables_result). There are two places where I_S table can be filled: JOIN::exec and create_sort_index(). To fix the bug we should check if the table was already filled in one of these places and skip processing of the table in second.
-
- 11 Feb, 2007 1 commit
-
-
evgen@moonbone.local authored
Post fix for bug#12122. information_schema.result: Corrected test case after fixing bug#12122.
-
- 01 Feb, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
additional call of file->extra() method with HA_EXTRA_NO_CACHE parameter
-
- 09 Dec, 2006 1 commit
-
-
patg@govinda.patg.net authored
Post-commit issues fixed * Test results for other tests fixed due to added error #s * Memory allocation/free issues found with running with valgrind * Fix to mysql-test-run shell script to run federated_server test (installs mysql.servers table properly)
-
- 01 Dec, 2006 2 commits
-
-
mskold/marty@mysql.com/linux.site authored
Changed mysql.apply_status, mysql.binlog_index, and mysql.schema to mysql.ndb_apply_status, mysql.ndb_binlog_index, and mysql.ndb_schema
-
thek@kpdesk.mysql.com authored
- Refactoring of duplicate code - Modified bad test cases - Changed expected error when operating on information_schema.
-
- 21 Nov, 2006 3 commits
-
-
monty@mysql.com/nosik.monty.fi authored
Moved .progress files into the log directory Moved 'cluster' database tables into the MySQL database, to not have 'cluster' beeing a reserved database name Fixed bug where mysqld got a core dump when trying to use a table created by MySQL 3.23 Fixed some compiler warnings Fixed small memory leak in libmysql Note that this doesn't changeset doesn't include the new mysqldump.c code required to run some tests. This will be added when I merge 5.0 to 5.1
-
gluh@mysql.com/gluh.(none) authored
-
gluh@mysql.com/gluh.(none) authored
disable filling of I_S tables for EXPLAIN
-
- 23 Oct, 2006 2 commits
-
-
andrey@example.com authored
-
andrey@example.com authored
To the documentor: The DEFAULT value in SHOW COLUMNS/SELECT FROM I_S.COLUMNS was truncated to NAME_LEN (which effectively is 64) characters.
-
- 13 Sep, 2006 1 commit
-
-
tables to INFORMATION_SCHEMA.
-
- 06 Sep, 2006 1 commit
-
-
igor@rurik.mysql.com authored
Select_type in the EXPLAIN output for the query SELECT * FROM t1 was 'SIMPLE', while for the query SELECT * FROM v1, where the view v1 was defined as SELECT * FROM t1, the EXPLAIN output contained 'PRIMARY' for the select_type column.
-
- 15 Aug, 2006 1 commit
-
-
stewart@willster.(none) authored
make test work both with and without ndbcluster
-
- 01 Aug, 2006 1 commit
-
-
evgen@sunlight.local authored
-
- 25 Jul, 2006 1 commit
-
-
igor@olga.mysql.com authored
a non-correlated single-row subquery over information schema. The function get_all_tables filling all information schema tables reset lex->sql_command to SQLCOM_SHOW_FIELDS. After this the function could evaluate partial conditions related to some columns. If these conditions contained a subquery over information schema it led to a wrong evaluation and a wrong result set. This bug was already fixed in 5.1. This patch follows the way how it was done in 5.1 where the value of lex->sql_command is set to SQLCOM_SHOW_FIELDS in get_all_tables only for the calls of the function open_normal_and_derived_tables and is restored after these calls.
-
- 22 Jul, 2006 1 commit
-
-
igor@olga.mysql.com authored
subqueries on information schema that use MIN/MAX aggregation. Execution of some correlated subqueries may set the value of null_row to 1 for tables used in the subquery. If the the subquery is on information schema it causes rejection of any row for the following executions of the subquery in the case when an optimization filtering by some condition is applied. The fix restores the value of the null_row flag for each execution of a subquery on information schema.
-
- 14 Jul, 2006 1 commit
-
-
kostja@bodhi.local authored
-
- 29 Jun, 2006 1 commit
-
-
kroki@mysql.com authored
SHOW CREATE PROCEDURE and SHOW CREATE FUNCTION are fixed as well as INFORMATION_SCHEMA.ROUTINES.ROUTINE_NAME.
-