- 26 Oct, 2005 9 commits
-
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
brian@zim.(none) authored
Change in gis test to allow NDB to be able to call generic tests. Fix for Archive so that ALTER TABLE doesn't issue a warning. Also added test case for alter table.
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/mysql-5.0
-
SergeyV@selena. authored
into selena.:H:/MYSQL/src/#14137-mysql-5.0
-
reggie@big_geek. authored
into big_geek.:C:/Work/mysql/mysql-5.0
-
SergeyV@selena. authored
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0
-
reggie@big_geek. authored
another macro defined in the Windows header files.
-
- 25 Oct, 2005 27 commits
-
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/mysql-5.0
-
sasha@asksasha.com authored
into asksasha.com:/reiser-data/mysql-dev/mysql-5.0-bug12974
-
pgalbraith@mysql.com authored
into mysql.com:/data0/mysqldev/patg/mysql-5.0-viewfix
-
pgalbraith@mysql.com authored
mysqldump.result: BUG# 12838 New test results for mysqldump -x on a DB with views mysqldump.test: sqldump.test: BUG# 12838 New test to run mysqldump -x on a DB with views mysqldump.c: BUG# 12838 Removed/Changed code which created tables to be put into the dump (For loading views of views) by creating temp tables and then using the CREATE TABLE information in those temp tables. The problem with this is that when mysqldump -x is called, it locks all tables, so the temp tables could not be created, causing the mysqldump to exit with failure. The code was changed to use SHOW FIELDS to get the column names and type to build CREATE TABLE text used to create these tables that views need in the dump.
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-5.0.12267
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-5.0.12267
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-5.0.12267
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-5.0.12267
-
acurtis@zim.(none) authored
into zim.(none):/home/acurtis/mysql-5.0-noraid.2
-
acurtis@zim.(none) authored
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/mysql-5.0
-
reggie@big_geek. authored
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-5.0.12267
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/5.0.b14207
-
pem@mysql.com authored
-
anozdrin@mysql.com authored
into mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.0-bug13037
-
anozdrin@mysql.com authored
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/5.0.b10303
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/mysql-5.0
-
brian@zim.(none) authored
-
brian@zim.(none) authored
-
timour@mysql.com authored
into mysql.com:/home/timka/mysql/src/5.0-bug-13832
-
timour@mysql.com authored
The cause for the bug is that the priorities of all rules/terminals that process the FROM clause are not fully specified, and the parser generator produces a parser that doesn't always parse the FROM clause so that JOINs are left-associative. As a result the final join tree produced by the parser is incorrect, which is the cause for subsequent name resolution to fail.
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0
-
kent@mysql.com authored
Option to set environment variable MTR_BUILD_THREAD to a small number, from what mysql-test-run calculate port numbers that will not conflict with other runs with different thread num
-
- 24 Oct, 2005 4 commits
-
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/mysql-5.0-enum-logtype
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/mysql-5.0-enum-logtype
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/mysql-5.0-base64
-
lars@mysql.com authored
-