An error occurred fetching the project authors.
- 17 Mar, 2006 1 commit
-
-
mats@mysql.com authored
Filter out replication general_log and slow_log entirely from binary log. Caching result of table share-specific tests.
-
- 09 Mar, 2006 1 commit
-
-
mats@mysql.com authored
Post-merge patches.
-
- 08 Mar, 2006 1 commit
-
-
mats@mysql.com authored
Changes according to review comments.
-
- 28 Feb, 2006 1 commit
-
-
holyfoot@deer.(none) authored
-
- 25 Feb, 2006 1 commit
-
-
guilhem@mysql.com authored
and new binlog format called "mixed" (which is statement-based except if only row-based is correct, in this cset it means if UDF or UUID is used; more cases could be added in later 5.1 release): SET GLOBAL|SESSION BINLOG_FORMAT=row|statement|mixed|default; the global default is statement unless cluster is enabled (then it's row) as in 5.1-alpha. It's not possible to use SET on this variable if a session is currently in row-based mode and has open temporary tables (because CREATE TEMPORARY TABLE was not binlogged so temp table is not known on slave), or if NDB is enabled (because NDB does not support such change on-the-fly, though it will later), of if in a stored function (see below). The added tests test the possibility or impossibility to SET, their effects, and the mixed mode, including in prepared statements and in stored procedures and functions. Caveats: a) The mixed mode will not work for stored functions: in mixed mode, a stored function will always be binlogged as one call and in a statement-based way (e.g. INSERT VALUES(myfunc()) or SELECT myfunc()). b) for the same reason, changing the thread's binlog format inside a stored function is refused with an error message. c) the same problems apply to triggers; implementing b) for triggers will be done later (will ask Dmitri). Additionally, as the binlog format is now changeable by each user for his session, I remove the implication which was done at startup, where row-based automatically set log-bin-trust-routine-creators to 1 (not possible anymore as a user can now switch to stmt-based and do nasty things again), and automatically set --innodb-locks-unsafe-for-binlog to 1 (was anyway theoretically incorrect as it disabled phantom protection). Plus fixes for compiler warnings.
-
- 24 Feb, 2006 1 commit
-
-
monty@mysql.com authored
(Needed for "list of pushes" web page and autopush)
-
- 16 Feb, 2006 1 commit
-
-
mats@mysql.com authored
Table maps are now written on aquiring locks to tables and released at the end of each logical statement.
-
- 14 Feb, 2006 1 commit
-
-
bar@mysql.com authored
Backporting character_set_filesystem from 5.0 to 5.1.
-
- 10 Feb, 2006 1 commit
-
-
joerg@mysql.com authored
Originally, done by Jani and pushed to the general 5.1 tree as ChangeSet 2006/02/02 16:22:31+02:00 jani@ua141d10.elisa.omakaista.fi now just copied to the 5.1.6 build clone.
-
- 02 Feb, 2006 1 commit
-
-
jani@ua141d10.elisa.omakaista.fi authored
-
- 19 Jan, 2006 1 commit
-
-
cps@outpost.site authored
CSV storage engine to be statically compiled. Derived from antony's patch.
-
- 18 Jan, 2006 2 commits
-
-
bell@sanja.is.com.ua authored
-
bar@mysql.com authored
Adding test case. sql_yacc.yy: Adding TEXT_STRING_filesystem, which converts from character_set_client to character_set_conversion. Replacing TEXT_STRING_sys to TEXT_STRING_filesystem in LOAD DATA and SELECT INTO OUTFILE contexts. sql_class.h, sql_class.cc: Adding character_set_filesystem variable, and charset_is_character_set_filesystem flag (to avoid conversion when it's not necessary). set_var.h, set_var.cc: Adding sys_var_character_set_filesystem mysqld.cc: Adding --character-set-filesystem startup option.
-
- 15 Jan, 2006 1 commit
-
-
aivanov@mysql.com authored
(reviewed by Mats)
-
- 13 Jan, 2006 1 commit
-
-
knielsen@mysql.com authored
-
- 10 Jan, 2006 2 commits
-
-
jani@ua141d10.elisa.omakaista.fi authored
-
joerg@mysql.com authored
cleaned up some of the casts as a result of Mats' review. (transferred from "2005/12/10 22:31:58-06:00 reggie@fedora.(none)" and from "2006/01/03 22:37:24-06:00 reggie@fedora.(none)")
-
- 09 Jan, 2006 1 commit
-
-
mats@mysql.com authored
-
- 04 Jan, 2006 4 commits
-
-
lars@mysql.com authored
-
mats@mysql.com authored
-
holyfoot@deer.(none) authored
Now it supports queries returning several results (particularly important with the SP)
-
reggie@fedora.(none) authored
-
- 30 Dec, 2005 1 commit
-
-
reggie@fedora.(none) authored
-
- 27 Dec, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 24 Dec, 2005 1 commit
-
-
mats@mysql.com authored
Added code for pending event flush just before executing the function or trigger.
-
- 22 Dec, 2005 2 commits
-
-
sergefp@mysql.com authored
-
lars@mysql.com authored
This includes both code and test cases.
-
- 14 Dec, 2005 1 commit
-
-
ramil@mysql.com authored
and bug #15668: Test 'sp-error' crashes server on Mac OS X.
-
- 07 Dec, 2005 1 commit
-
-
anozdrin@mysql.com authored
according to the standard. The idea is to use Field-classes to implement stored routines variables. Also, we should provide facade to Item-hierarchy by Item_field class (it is necessary, since SRVs take part in expressions). The patch fixes the following bugs: - BUG#8702: Stored Procedures: No Error/Warning shown for inappropriate data type matching; - BUG#8768: Functions: For any unsigned data type, -ve values can be passed and returned; - BUG#8769: Functions: For Int datatypes, out of range values can be passed and returned; - BUG#9078: STORED PROCDURE: Decimal digits are not displayed when we use DECIMAL datatype; - BUG#9572: Stored procedures: variable type declarations ignored; - BUG#12903: upper function does not work inside a function; - BUG#13705: parameters to stored procedures are not verified; - BUG#13808: ENUM type stored procedure parameter accepts non-enumerated data; - BUG#13909: Varchar Stored Procedure Parameter always BINARY string (ignores CHARACTER SET); - BUG#14161: Stored procedure cannot retrieve bigint unsigned; - BUG#14188: BINARY variables have no 0x00 padding; - BUG#15148: Stored procedure variables accept non-scalar values;
-
- 01 Dec, 2005 1 commit
-
-
ramil@mysql.com authored
Fix for bug #14304: auto_increment field incorrect set from within stored procedure (insert select).
-
- 30 Nov, 2005 1 commit
-
-
timour@mysql.com authored
The cause of the bug was the use of end_write_group instead of end_write in the case when ORDER BY required a temporary table, which didn't take into account the fact that loose index scan already computes the result of MIN/MAX aggregate functions (and performs grouping). The solution is to call end_write instead of end_write_group and to add the MIN/MAX functions to the list of regular functions so that their values are inserted into the temporary table.
-
- 24 Nov, 2005 1 commit
-
-
pem@mysql.com authored
-
- 23 Nov, 2005 3 commits
-
-
monty@mysql.com authored
The table opening process now works the following way: - Create common TABLE_SHARE object - Read the .frm file and unpack it into the TABLE_SHARE object - Create a TABLE object based on the information in the TABLE_SHARE object and open a handler to the table object Other noteworthy changes: - In TABLE_SHARE the most common strings are now LEX_STRING's - Better error message when table is not found - Variable table_cache is now renamed 'table_open_cache' - New variable 'table_definition_cache' that is the number of table defintions that will be cached - strxnmov() calls are now fixed to avoid overflows - strxnmov() will now always add one end \0 to result - engine objects are now created with a TABLE_SHARE object instead of a TABLE object. - After creating a field object one must call field->init(table) before using it - For a busy system this change will give you: - Less memory usage for table object - Faster opening of tables (if it's has been in use or is in table definition cache) - Allow you to cache many table definitions objects - Faster drop of table
-
konstantin@mysql.com authored
check_stack_overrun().
-
bell@sanja.is.com.ua authored
-
- 22 Nov, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
if inner routine has more local variables than outer one, and one of its last variables was used as argument to NOT operator". THD::spcont was non-0 when we were parsing stored routine/trigger definition during execution of another stored routine. This confused methods of Item_splocal and forced them use wrong runtime context. Fix ensures that we always have THD::spcont equal to zero during routine/trigger body parsing. This also allows to avoid problems with errors which occur during parsing and SQL exception handlers.
-
- 19 Nov, 2005 1 commit
-
-
dlenev@mysql.com authored
handling of savepoints in stored routines. Fixed ha_rollback_to_savepoint()/ha_savepoint()/ha_release_savepoint() functions to properly handle savepoints inside of stored functions and triggers. Also now when we invoke stored function or trigger we create new savepoint level. We destroy it at the end of function/trigger execution and return back to old savepoint level.
-
- 15 Nov, 2005 1 commit
-
-
ingo@mysql.com authored
Version for 5.0. It fixes three problems: 1. The cause of the bug was that we did not check the table version for the HANDLER ... READ commands. We did not notice when a table was replaced by a new one. This can happen during ALTER TABLE, REPAIR TABLE, and OPTIMIZE TABLE (there might be more cases). I call the fix for this problem "the primary bug fix". 2. mysql_ha_flush() was not always called with a locked LOCK_open. Though the function comment clearly said it must. I changed the code so that the locking is done when required. I call the fix for this problem "the secondary fix". 3. In 5.0 (not in 4.1 or 4.0) DROP TABLE had a possible deadlock flaw in concur with FLUSH TABLES WITH READ LOCK. I call the fix for this problem "the 5.0 addendum fix".
-
- 07 Nov, 2005 1 commit
-
-
acurtis@poseidon.ndb.mysql.com authored
-
- 03 Nov, 2005 1 commit
-
-
ingo@mysql.com authored
Version for 4.0. It fixes two problems: 1. The cause of the bug was that we did not check the table version for the HANDLER ... READ commands. We did not notice when a table was replaced by a new one. This can happen during ALTER TABLE, REPAIR TABLE, and OPTIMIZE TABLE (there might be more cases). I call the fix for this problem "the primary bug fix". 2. mysql_ha_flush() was not always called with a locked LOCK_open. Though the function comment clearly said it must. I changed the code so that the locking is done when required. I call the fix for this problem "the secondary fix".
-