- 21 Jul, 2006 1 commit
-
-
unknown authored
The problem was that store_top_level_join_columns() incorrectly assumed that the left/right neighbor of a nested join table reference can be only at the same level in the join tree. The fix checks if the current nested join table reference has no immediate left/right neighbor, and if so chooses the left/right neighbors of the nearest upper level, where these references are != NULL. mysql-test/r/group_min_max.result: Test for BUG#21007. mysql-test/t/group_min_max.test: Test for BUG#21007. sql/sql_base.cc: After computing and materializing the columns of all NATURAL joins in a FROM clause, the procedure store_top_level_join_columns() has to change the current natural join into a leaf table reference for name resolution. For this it needs to make the left neighbor point to the natural join table reference, and the natural join itself point to its left neighbor. This fix correctly determines the left/right neighbors of a table reference, even if the neghbors are at higher levels in the nested join tree. The rule is that if a table reference has no immediate left/right neighbors, we recursively pick the left/right neighbor of the level(s) above.
-
- 15 Jul, 2006 1 commit
-
-
unknown authored
into orca.ndb.mysql.com:/space_old/pekka/ndb/version/my50
-
- 14 Jul, 2006 3 commits
- 13 Jul, 2006 12 commits
-
-
unknown authored
client/mysql.cc: Auto merged client/sql_string.h: Auto merged configure.in: Auto merged myisam/mi_create.c: Auto merged mysql-test/r/date_formats.result: Auto merged mysql-test/t/date_formats.test: Auto merged ndb/src/kernel/blocks/dbtup/DbtupMeta.cpp: Auto merged ndb/src/mgmsrv/ConfigInfo.cpp: Auto merged sql/item_strfunc.cc: Auto merged sql/sql_class.cc: Auto merged sql/sql_string.h: Auto merged sql/table.cc: Auto merged
-
unknown authored
into mysql.com:/home/tnurnberg/work/mysql-5.0-21014
-
unknown authored
mysqldump did not select the correct database before trying to dump views from it. this resulted in an empty result set, which in turn startled mysql-dump into a core-dump. this only happened for views, not for tables, and was only visible with multiple databases that weren't by sheer luck in the order mysqldump required, anyway. this fixes by selecting the correct database before dumping views; it also catches the empty set-condition if it should occur for other reasons. client/mysqldump.c: Bug#21014: Segmentation fault of mysqldump on view failsafe: if "select ... from information_schema.views" returns an empty set, don't deref NULL; throw an error instead. fix: select the correct database not only before dumping tables, but before dumping views, as well. mysql-test/r/mysqldump.result: Bug#21014: Segmentation fault of mysqldump on view show that mysqldump selects the correct database before trying to dump views from it. mysql-test/t/mysqldump.test: Bug#21014: Segmentation fault of mysqldump on view show that mysqldump selects the correct database before trying to dump views from it.
-
unknown authored
into zippy.(none):/home/cmiller/work/mysql/m41-maint--07AB5
-
unknown authored
into zippy.(none):/home/cmiller/work/mysql/m41-maint--07AB5
-
unknown authored
into zippy.(none):/home/cmiller/work/mysql/m50--07C2P
-
unknown authored
into zippy.(none):/home/cmiller/work/mysql/m50-maint--07C2P
-
unknown authored
into zippy.(none):/home/cmiller/work/mysql/m50-maint--07C2P configure.in: Auto merged mysql-test/mysql-test-run.pl: Auto merged tests/mysql_client_test.c: manual merge
-
unknown authored
scripts/mysql_explain_log.sh: Changed explain_log.pl to mysql_explain_log. Added usage information for printerror. Minor cleanup.
-
unknown authored
into mysql.com:/home/hf/work/mysql-5.0.clean sql-common/client.c: Auto merged sql/item_strfunc.cc: Auto merged
-
unknown authored
into anubis.greendragongames.com:/home/greenman/workspace-mysql/mysql/pending/bug-4.1-15977
-
unknown authored
do not look for client-specific commands while inside a multi-line comment. we will allow multi-comments pretty much anywhere within SQL-statements, but client-specific commands (help, use, print, ...) must be the first token in the input. client/mysql.cc: Bug#20432: mysql client interprets commands in comments mysql-test/r/mysql_client.result: Bug#20432: mysql client interprets commands in comments test client-side parsing of comments and client-specific commands mysql-test/t/mysql_client.test: Bug#20432: mysql client interprets commands in comments test client-side parsing of comments and client-specific commands
-
- 12 Jul, 2006 6 commits
-
-
unknown authored
into zippy.(none):/home/cmiller/work/mysql/m50-maint--07C2P configure.in: Auto merged
-
unknown authored
sql/item_timefunc.cc: Fix a valgrind warning in type_date test.
-
unknown authored
The bug is thqt we use some nonstandard assembly codes in our strings source, and some assemblers don't know what to do with them: Specifically, Sun's Solaris assembler and Apple's Darwin assembler balk at them. This patch, rather than trying to test for properties of the assembler, which Autoconf doesn't have any decent facilites for, instead tries to compile the code in question and disables assembly if it fails. There's still the problem of unportable assembly, but I'll leave that to someone who feels like rewriting and debugging it. configure.in: Actually try to compile the code in question, since a test for the CPU type is insufficient to determine whether our code will compile.
-
unknown authored
into dl145k.mysql.com:/data0/mkindahl/bk/mysql-5.0-rpl ndb/include/kernel/GlobalSignalNumbers.h: Auto merged ndb/src/kernel/blocks/dbdict/Dbdict.cpp: Auto merged ndb/src/kernel/blocks/dbdict/Dbdict.hpp: Auto merged ndb/src/kernel/blocks/dbdih/DbdihMain.cpp: Auto merged ndb/src/ndbapi/ndberror.c: Auto merged sql/ha_ndbcluster.cc: Auto merged sql/handler.h: Auto merged sql/sql_base.cc: Auto merged sql/sql_insert.cc: Auto merged
-
unknown authored
into dl145k.mysql.com:/data0/mkindahl/bk/mysql-4.1-rpl
-
unknown authored
into maint1.mysql.com:/data/localhome/cmiller/mysql-4.1
-
- 11 Jul, 2006 10 commits
-
-
unknown authored
into zippy.(none):/home/cmiller/work/mysql/m41-maint--07AB5 mysql-test/r/date_formats.result: Auto merged mysql-test/t/date_formats.test: Auto merged
-
unknown authored
The problem is that the author used the wrong function to send a warning to the user about truncation of data. push_warning() takes a constant string and push_warning_printf() takes a format and variable arguments to fill it. Since the string we were complaining about contains percent characters, the printf() code interprets the "%Y" et c. that the user sends. That's wrong, and often causes a crash, especially if the date mentions seconds, "%s". A alternate fix would be to use push_warning_printf(..., "%s", warn_buff) . mysql-test/r/date_formats.result: Test that an invalid date doesn't crash the server. We should get a warning back instead of a dead socket. mysql-test/t/date_formats.test: Test that an invalid date doesn't crash the server. We should get a warning back instead of a dead socket. sql/time.cc: Don't try to use warn_buf as the start of a varible arguement list to send to a warning-formatted my_vsnprintf() .
-
unknown authored
ndb/src/kernel/error/TimeModule.cpp: 0=Sunday
-
unknown authored
into bodhi.local:/opt/local/work/mysql-5.0-runtime-merge-41 sql/sql_table.cc: Auto merged
-
unknown authored
into zippy.(none):/home/cmiller/work/mysql/merge/mysql-4.1 client/sql_string.h: Auto merged sql/item_func.h: Auto merged sql/sql_string.h: Auto merged configure.in: Null merge. sql/item_strfunc.cc: Null merged
-
unknown authored
into chilla.local:/home/mydev/mysql-5.0-amerge sql/handler.h: Auto merged sql/sql_table.cc: Auto merged
-
unknown authored
-
unknown authored
into trift2.:/M50/mysql-5.0
-
unknown authored
into dl145k.mysql.com:/data0/mkindahl/bk/MERGE/mysql-5.0-merge ndb/include/kernel/GlobalSignalNumbers.h: Auto merged ndb/src/kernel/blocks/dbdict/Dbdict.cpp: Auto merged ndb/src/kernel/blocks/dbdict/Dbdict.hpp: Auto merged ndb/src/kernel/blocks/dbdih/DbdihMain.cpp: Auto merged ndb/src/ndbapi/ndberror.c: Auto merged
-
unknown authored
into bodhi.local:/opt/local/work/mysql-5.0-runtime-merge-41 sql/opt_range.cc: Auto merged support-files/mysql.spec.sh: Auto merged mysql-test/Makefile.am: Manual merge.
-
- 10 Jul, 2006 7 commits
-
-
unknown authored
sql/sql_locale.cc: "true" -> TRUE
-
unknown authored
into trift2.:/M50/mysql-5.0 configure.in: Auto merged
-
unknown authored
-
unknown authored
the server's binlog file, might be set to a different directory. This adds a new "vardir" parameter, which takes the name of the directory as a value, so that the test_bug17667() test can find the binlog. mysql-test/mysql-test-run.pl: Add the "vardir" to the options passed to "mysql_test_client", so we know where to find the binlog file. tests/mysql_client_test.c: Receive a new option, "vardir". Use the vardir option to find the binlog file in test_bug17667() .
-
unknown authored
sql/sql_locale.cc: Fix Windows compilation failure "cannot convert from 'const char [6]' to 'const BOOL'" and an apparent bug (use of "FALSE" instead of FALSE for initialization of is_ascii member of MY_LOCALE)
-
unknown authored
-
unknown authored
into gbichot3.local:/home/mysql_src/mysql-5.0
-