- 14 Aug, 2005 1 commit
-
-
serg@sergbook.mysql.com authored
mysql default port cleanup (it's set in libmysql.c, NOT in my_getopt) configure.in autoconf 2.52 is enough to build mysql-5.0
-
- 13 Aug, 2005 1 commit
-
-
serg@sergbook.mysql.com authored
-
- 12 Aug, 2005 22 commits
-
-
serg@sergbook.mysql.com authored
-
serg@sergbook.mysql.com authored
Now we keep all active XID's in a hash
-
evgen@moonbone.local authored
view being created. Item_func_timestamp_diff::func_name() were returning function name as "timestamp_diff" thus when view was executed function parameters wasn't properly recognized and error was raised.
-
timour@mysql.com authored
Disabled one test case because it is still a problem due to the fix for WL#2486. Pushed to enable code review.
-
timour@mysql.com authored
into mysql.com:/home/timka/mysql/src/5.0-2486-merge
-
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
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-5.0
-
osku@127.(none) authored
into 127.(none):/home/osku/mysql-5.0
-
bar@mysql.com authored
After merge change. 4.1 method was replaced in 5.0.
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-5.0-build
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-5.0
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-4.1.b12351
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-5.0-build
-
igor@rurik.mysql.com authored
A safety correction.
-
osku@127.(none) authored
into 127.(none):/home/osku/mysql-5.0
-
osku@127.(none) authored
most notably deadlocked ones in SHOW INNODB STATUS. Fixes bug #7819.
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
Fixed bug #12470. A misplaced initialization of the cond_count counter resulted in a wrong calculation of it. This caused a memory corruption since this counter was used as a parameter of some memory allocation. view.test: Added a test case for bug #12470.
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.1-merge
-
jimw@mysql.com authored
number of seconds (which can include microseconds). (Bug #6760)
-
patg@radha.local authored
into radha.local:/Users/patg/mysql-build/mysql-4.1.clean
-
jimw@mysql.com authored
earlier change wasn't correct. (But the other changes to the test were.)
-
- 11 Aug, 2005 16 commits
-
-
igor@rurik.mysql.com authored
Fixed bug #12382. INSERT statement effectively changed thd->set_query_id to 0, while SELECT statement changed it to 0. As a result the insert_fields function that expanded '*' was called with different values of thd->set_query_id for the query SELECT * FROM view depending on whether it was run after an INSERT or after a SELECT statement. This was corrected by restoring the old value of thd->set_query_id when returning from the function setup_fields where possible reset could occur. If the value of thd->set_query_id == 0 then the fields substituted instead of '*' were not registered as used for bitmaps used_keys. This caused selection of an invalid execution plan for the query SELECT * from <view>. view.result, view.test: Added a test case for bug #12382.
-
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
-
jimw@mysql.com authored
automatically. (Bug #12324)
-
lenz@mysql.com authored
-
lenz@mysql.com authored
preflight/postflight instead, so they are run every time a PKG is installed, not only for a fresh installation
-
vtkachenko@quadxeon.mysql.com authored
into quadxeon.mysql.com:/users/vtkachenko/bk/mysql-5.0-tmp
-
lenz@mysql.com authored
change was too drastic) (BUG#12506)
-
acurtis@xiphis.org authored
into xiphis.org:/usr/home/antony/work2/merge-5.0
-
acurtis@xiphis.org authored
-
jani@ua141d10.elisa.omakaista.fi authored
sql_print_warning() and sql_print_error() instead of fprintf to stderr. Above functions are tuned for different platforms so that the behavior is consistent around platforms. Using fprintf() different behavior can be expected at least on Windows and Unix.
-
vtkachenko@quadxeon.mysql.com authored
Added innodb_commit_concurrency variable
-
acurtis@xiphis.org authored
into xiphis.org:/usr/home/antony/work2/merge-5.0
-
sanja@arthur.local authored
postmerge fix
-
bell@51.0.168.192.in-addr.arpa authored
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-bg11973-2
-