- 25 Oct, 2005 21 commits
-
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/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
-
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
-
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 16 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
-
anozdrin@mysql.com authored
into mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.0-bug13095
-
anozdrin@mysql.com authored
into mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.0-bug13095
-
anozdrin@mysql.com authored
- allow CREATE VIEW as well as DROP VIEW to use in prepared statements; - fix CREATE VIEW implementation to make it work in prepared statements.
-
patg@krsna.patg.net authored
into krsna.patg.net:/home/patg/mysql-build/mysql-5.0.test2
-
patg@krsna.patg.net authored
federated.disabled and instead using disabled.def (per comments in this commit) disabled.def: disabled federated until bug 14272 is fixed. .del-federated.disabled~9e4cca59f547174d: Delete: mysql-test/t/federated.disabled federated.disabled: New BitKeeper file ``t/federated.disabled'' to disable federated test until Bug 14272 is fixed. new file
-
sergefp@mysql.com authored
OPTIMIZE TABLE.
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/mysql-5.0-base64
-
lars@mysql.com authored
different features, adding numbering to enums reduce the risk that code will be merged incorrectly. This particular enum must have fixed values to ensure that an upgraded server always can read old logs. I added this, since I noticed the incorrect order in the RBR clone.
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/mysql-5.0-hexdump
-
msvensson@neptunus.mysql.com authored
-
ramil@mysql.com authored
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/5.0.b10303
-
- 23 Oct, 2005 1 commit
-
-
sasha@asksasha.com authored
-
- 21 Oct, 2005 2 commits
-
-
pem@mysql.com authored
into mysql.com:/usr/home/pem/bug13941/mysql-5.0
-
bar@mysql.com authored
After merge fix.
-