An error occurred fetching the project authors.
- 23 May, 2007 1 commit
-
-
dlenev@mockturtle.local authored
Bug #23667 "CREATE TABLE LIKE is not isolated from alteration by other connections" Bug #18950 "CREATE TABLE LIKE does not obtain LOCK_open" As well as: Bug #25578 "CREATE TABLE LIKE does not require any privileges on source table". The first and the second bugs resulted in various errors and wrong binary log order when one tried to execute concurrently CREATE TABLE LIKE statement and DDL statements on source table or DML/DDL statements on its target table. The problem was caused by incomplete protection/table-locking against concurrent statements implemented in mysql_create_like_table() routine. We solve it by simply implementing such protection in proper way (see comment for sql_table.cc for details). The third bug allowed user who didn't have any privileges on table create its copy and therefore circumvent privilege check for SHOW CREATE TABLE. This patch solves this problem by adding privilege check, which was missing. Finally it also removes some duplicated code from mysql_create_like_table(). Note that, altough tests covering concurrency-related aspects of CREATE TABLE LIKE behaviour will only be introduced in 5.1, they were run manually for this patch as well.
-
- 30 Mar, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
ARCHIVE table ARCHIVE table was truncated by REPAIR TABLE ... USE_FRM statement. The table handler returned its file name extensions in a wrong order. REPAIR TABLE believed it has to use the meta file to create a new table from it. With the fixed order, REPAIR TABLE does now use the data file to create a new table. So REPAIR TABLE ... USE_FRM works well with ARCHIVE engine now. This issue affects 5.0 only, since in 5.1 ARCHIVE engine stores meta information and data in the same file.
-
- 31 Dec, 2006 1 commit
-
-
kent@mysql.com/kent-amd64.(none) authored
Corrected spelling in copyright text Makefile.am: Don't update the files from BitKeeper Many files: Removed "MySQL Finland AB & TCX DataKonsult AB" from copyright header Adjusted year(s) in copyright header Many files: Added GPL copyright text Removed files: Docs/Support/colspec-fix.pl Docs/Support/docbook-fixup.pl Docs/Support/docbook-prefix.pl Docs/Support/docbook-split Docs/Support/make-docbook Docs/Support/make-makefile Docs/Support/test-make-manual Docs/Support/test-make-manual-de Docs/Support/xwf
-
- 23 Dec, 2006 1 commit
-
-
kent@mysql.com/kent-amd64.(none) authored
Changed header to GPL version 2 only
-
- 12 Sep, 2006 1 commit
-
-
svoj@april.(none) authored
Only MyISAM tables locked with LOCK TABLES ... WRITE were affected. A query that is optimized with index_merge doesn't reflect rows inserted within LOCK TABLES. MyISAM doesn't flush a state within LOCK TABLES. index_merge optimization creates a copy of the handler, which thus gets outdated MyISAM state. New handler->clone() method is introduced to fix this problem. For non-MyISAM storage engines it allocates a handler and opens it with ha_open(). For MyISAM it additionally copies MyISAM state pointer to cloned handler.
-
- 30 Aug, 2006 1 commit
-
-
"strict mode: inserts autogenerated auto_increment value bigger than max" Strict mode should fail if autoincrement value is out of range
-
- 10 Aug, 2006 1 commit
-
-
stewart@willster.(none) authored
allow handler::info to return an error code (that will be returned to the user)
-
- 10 Jul, 2006 1 commit
-
-
ingo/mydev@chilla.local authored
-
- 05 Jul, 2006 1 commit
-
-
guilhem@mysql.com authored
auto_increment breaks binlog": if slave's table had a higher auto_increment counter than master's (even though all rows of the two tables were identical), then in some cases, REPLACE and INSERT ON DUPLICATE KEY UPDATE failed to replicate statement-based (it inserted different values on slave from on master). write_record() contained a "thd->next_insert_id=0" to force an adjustment of thd->next_insert_id after the update or replacement. But it is this assigment introduced indeterminism of the statement on the slave, thus the bug. For ON DUPLICATE, we replace that assignment by a call to handler::adjust_next_insert_id_after_explicit_value() which is deterministic (does not depend on slave table's autoinc counter). For REPLACE, this assignment can simply be removed (as REPLACE can't insert a number larger than thd->next_insert_id). We also move a too early restore_auto_increment() down to when we really know that we can restore the value.
-
- 04 Jul, 2006 1 commit
-
-
tomas@poseidon.ndb.mysql.com authored
- partial backport of code from 5.1, do cot compare_record for engines that do not read all columns during update
-
- 29 Jun, 2006 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
Table comment: issue a warning(error in traditional mode) if length of comment > 60 symbols Column comment: issue a warning(error in traditional mode) if length of comment > 255 symbols Table 'comment' is changed from char* to LEX_STRING
-
- 02 Jun, 2006 1 commit
-
-
mskold@mysql.com authored
-
- 09 May, 2006 1 commit
-
-
acurtis@xiphis.org authored
"alter table from MyISAM to MERGE lost data without errors and warnings" Add new handlerton flag which prevent user from altering table storage engine to storage engines which would lose data. Both 'blackhole' and 'merge' are marked with the new flag. Tests included.
-
- 13 Apr, 2006 2 commits
-
-
grog@mysql.com[grog] authored
-
grog@mysql.com[grog] authored
-
- 12 Apr, 2006 1 commit
-
-
holyfoot@deer.(none) authored
-
- 25 Feb, 2006 1 commit
-
-
monty@mysql.com authored
- Added empty constructors and virtual destructors to many classes and structs - Removed some usage of the offsetof() macro to instead use C++ class pointers
-
- 17 Feb, 2006 1 commit
-
-
holyfoot@deer.(none) authored
necessary implementation in the server mysql_upgrade script added
-
- 26 Nov, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 10 Nov, 2005 1 commit
-
-
brian@zim.(none) authored
-
- 03 Nov, 2005 1 commit
-
-
konstantin@mysql.com authored
large table gives server crash": make sure that when a MyISAM temporary table is created for a cursor, it's created in its memory root, not the memory root of the current query.
-
- 02 Nov, 2005 1 commit
-
-
igor@rurik.mysql.com authored
new file sql_table.cc, handler.h: Fixed bug #14540. Added error mnemonic code HA_ADMIN_NOT_BASE_TABLE to report that an operation cannot be applied for views. view.test, view.result: Added a test case for bug #14540. errmsg.txt: Fixed bug #14540. Added error ER_CHECK_NOT_BASE_TABLE.
-
- 10 Oct, 2005 1 commit
-
-
svoj@mysql.com authored
-
- 05 Oct, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 04 Oct, 2005 1 commit
-
-
brian@zim.(none) authored
Final patch for 5.0 for simplifying storage engine code. We now have just one set of ifdefs. I may also remove the code for creating new handlers. May changes were to simplify storage engine setup and support for legacy call to show storage engines.
-
- 03 Oct, 2005 1 commit
-
-
brian@zim.(none) authored
Handlerton array is now created instead of using sys_table_types_st. All storage engines can now have inits and giant ifdef's are now gone for startup. No compeltely clean yet, handlertons will next be merged with sys_table_types. Federated and archive now have real cleanup if their inits fail.
-
- 30 Sep, 2005 3 commits
-
-
eric@mysql.com authored
BUG#13108
-
serg@serg.mylan authored
"SELECT ... FOR UPDATE executed as consistent read inside LOCK TABLES" Do not discard lock_type information as handler::start_stmt() may require knowledge. (fixed by Antony)
-
sergefp@mysql.com authored
HA_KEY_SCAN_NOT_ROR index flag) as NDB index scans are not guaranteed to be ROR scans.
-
- 22 Sep, 2005 1 commit
-
-
brian@zim.(none) authored
The alias structure now is a bit more simple and just uses a pointer to replace with the currect name. The giant case statement should go away in the next patch.
-
- 20 Sep, 2005 1 commit
-
-
sergefp@mysql.com authored
statistics (like 4.0 did) (patch #3, with review #1 & #2 feedback addressed)
-
- 19 Sep, 2005 1 commit
-
-
brian@zim.(none) authored
Cleanup for handlerton structure to allow for loadable engine work. This is the first in a series of patches.
-
- 13 Sep, 2005 1 commit
-
-
eric@mysql.com authored
(per Monty's patch). Remove references to the "COMMENT" field. WL#2414
-
- 30 Aug, 2005 1 commit
-
-
osku@127.(none) authored
-
- 29 Aug, 2005 1 commit
-
-
brian@zim.(none) authored
-
- 17 Aug, 2005 1 commit
-
-
osku@127.(none) authored
in InnoDB tables.
-
- 12 Aug, 2005 1 commit
-
-
serg@sergbook.mysql.com authored
Now we keep all active XID's in a hash
-
- 20 Jul, 2005 1 commit
-
-
konstantin@mysql.com authored
cursors. This should fix Bug#11813 when InnoDB part is in (tested with a draft patch). The idea of the patch is that if a storage engine supports consistent read views, we open one when open a cursor, set is as the active view when fetch from the cursor, and close together with cursor close.
-
- 19 Jul, 2005 1 commit
-
-
konstantin@mysql.com authored
The idea of the patch is that every cursor gets its own lock id for table level locking. Thus cursors are protected from updates performed within the same connection. Additionally a list of transient (must be closed at commit) cursors is maintained and all transient cursors are closed when necessary. Lastly, this patch adds support for deadlock timeouts to TLL locking when using cursors. + post-review fixes.
-
- 17 Jun, 2005 1 commit
-
-
acurtis@xiphis.org authored
Implement new SQL mode - NO_ENGINE_SUBSTITUTION
-