An error occurred fetching the project authors.
- 30 Sep, 2005 1 commit
-
-
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)
-
- 29 Sep, 2005 2 commits
-
-
jan@hundin.mysql.fi authored
i.e. range test.
-
jan@hundin.mysql.fi authored
consistent read (Bug #12669). This fixes InnoDB part of the bug.
-
- 28 Sep, 2005 1 commit
-
-
jan@hundin.mysql.fi authored
consistent read (Bug #12669).
-
- 23 Sep, 2005 2 commits
-
-
osku@127.(none) authored
-
osku@127.(none) authored
-
- 19 Sep, 2005 1 commit
-
-
evgen@moonbone.local authored
This is backport from 5.0 of fix for bug #11039
-
- 13 Sep, 2005 1 commit
-
-
monty@mishka.mysql.fi authored
Added flag to Field::store(longlong) to specify if value is unsigned. This fixes bug #12750: Incorrect storage of 9999999999999999999 in DECIMAL(19, 0) Fixed warning from valgrind in CREATE ... SELECT Fixed double free of mysql.options if reconnect failed
-
- 12 Sep, 2005 1 commit
-
-
monty@mishka.mysql.com authored
Fix for bug #13025; Server crash in filesort because wrong call to handler::position()
-
- 06 Sep, 2005 1 commit
-
-
osku@127.(none) authored
-
- 31 Aug, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
- Add stricter checking of syntax in mysqltest
-
- 29 Aug, 2005 1 commit
-
-
ingo@mysql.com authored
Handle temporary tables like permanent tables: If the storage engine cannot truncate, delete instead.
-
- 23 Aug, 2005 1 commit
-
-
timour@mysql.com authored
* Provide backwards compatibility extension to name resolution of coalesced columns. The patch allows such columns to be qualified with a table (and db) name, as it is in 4.1. Based on a patch from Monty. * Adjusted tests accordingly to test both backwards compatible name resolution of qualified columns, and ANSI-style resolution of non-qualified columns. For this, each affected test has two versions - one with qualified columns, and one without.
-
- 19 Aug, 2005 1 commit
-
-
andrey@lmy004. authored
-
- 17 Aug, 2005 1 commit
-
-
osku@127.(none) authored
in InnoDB tables.
-
- 12 Aug, 2005 1 commit
-
-
timour@mysql.com authored
"Process NATURAL and USING joins according to SQL:2003". * Some of the main problems fixed by the patch: - in "select *" queries the * expanded correctly according to ANSI for arbitrary natural/using joins - natural/using joins are correctly transformed into JOIN ... ON for any number/nesting of the joins. - column references are correctly resolved against natural joins of any nesting and combined with arbitrary other joins. * This patch also contains a fix for name resolution of items inside the ON condition of JOIN ... ON - in this case items must be resolved only against the JOIN operands. To support such 'local' name resolution, the patch introduces a stack of name resolution contexts used at parse time. NOTICE: - This patch is not complete in the sense that - there are 2 test cases that still do not pass - one in join.test, one in select.test. Both are marked with a comment "TODO: WL#2486". - it does not include a new test specific for the task
-
- 09 Aug, 2005 1 commit
-
-
evgen@moonbone.local authored
When PRIMARY KEY is present ha_innobase::cmp_ref() uses it to compare refs. After comparing part of key it moves pointers to compare next part. For varchar parts pointers were moved only by length of parts, not including bytes containig part length itself. This results in wrong comparision and wrong number of deleted records.
-
- 28 Jul, 2005 1 commit
-
-
monty@mysql.com authored
-
- 14 Jul, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 20 Jun, 2005 1 commit
-
-
msvensson@neptunus.(none) authored
- Print warning that says display width is not supported for datatype TIMESTAMP, if user tries to create a TIMESTAMP column with display width. - Use display width for TIMESTAMP only in type_timestamp test to make sure warning is displayed correctly.
-
- 07 Jun, 2005 2 commits
-
-
heikki@hundin.mysql.fi authored
Update Monty's tests for AUTO-INC bug #11080 and bug #11005
-
heikki@hundin.mysql.fi authored
Update Monty's tests for AUTO-INC bug #11080 and bug #11005
-
- 06 Jun, 2005 2 commits
-
-
monty@mysql.com authored
This fixes bug #11080: Multi-row REPLACE fails on a duplicate key error
-
monty@mysql.com authored
Fixed wrong key length when using MIN() optimization (non fatal, but caused InnoDB to write warnings to the log file) This fixed bug #11039: InnoDB: Warning: using a partial-field key prefix in search
-
- 03 Jun, 2005 1 commit
-
-
monty@mysql.com authored
Ensure that 'null_value' is not accessed before val() is called in FIELD() functions Fixed initialization of key maps. This fixes some problems with keys when you have more than 64 keys Fixed that ROLLUP don't always create a temporary table. This fix ensures that func_gconcat.test results are now predictable
-
- 27 May, 2005 1 commit
-
-
lars@mysql.com authored
-
- 07 May, 2005 2 commits
-
-
svoj@mysql.com authored
-
svoj@mysql.com authored
fail.
-
- 06 May, 2005 1 commit
-
-
ramil@ram-book.(none) authored
-
- 14 Apr, 2005 1 commit
-
-
serg@serg.mylan authored
bug#8151
-
- 12 Apr, 2005 1 commit
-
-
ramil@mysql.com authored
-
- 04 Apr, 2005 1 commit
-
-
jimw@mysql.com authored
server testing cleanups.
-
- 30 Mar, 2005 1 commit
-
-
jimw@mysql.com authored
-
- 16 Mar, 2005 2 commits
-
-
monty@mysql.com authored
Enabled VARCHAR testing for innodb NOTE: innodb.test currently fails becasue of a bug in InnoDB. I have informed Heikki about this and expect him to fix this ASAP
-
dlenev@brandersnatch.localdomain authored
-
- 11 Mar, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 02 Mar, 2005 1 commit
-
-
serg@serg.mylan authored
deadlock in MYSQL_LOG::new_file() style fixes
-
- 24 Feb, 2005 1 commit
-
-
monty@mysql.com authored
Previously we only stored the first given error (the error sent to the client)
-
- 23 Feb, 2005 1 commit
-
-
serg@serg.mylan authored
new tests
-
- 21 Feb, 2005 1 commit
-
-
ramil@mysql.com authored
"create table ta(a bit...) engine=innodb" moved to innodb.test
-