- 15 Aug, 2005 9 commits
-
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com authored
-
monty@mysql.com authored
This allows us to use statement replication with functions and triggers The following things are fixed with this patch: - NOW() and automatic timestamps takes the value from the main event for functions and triggers (which allows these to replicate with statement level logging) - No side effects for triggers or functions with auto-increment values(), last_insert_id(), rand() or found_rows() - Triggers can't return result sets Fixes bugs: #12480: NOW() is not constant in a trigger #12481: Using NOW() in a stored function breaks statement based replication #12482: Triggers has side effects with auto_increment values #11587: trigger causes lost connection error
-
lenz@mysql.com authored
CFBundleShortVersionString in Info.plist may not include a version suffix like "-beta" (BUG#12584) - Minor cleanup: removed two unused keys from Info.plist: IFMajorVersion and IFMinorVersion
-
serg@sergbook.mysql.com authored
into sergbook.mysql.com:/usr/home/serg/Abk/mysql-5.0
-
evgen@moonbone.local authored
into moonbone.local:/work/mysql-5.0-bug-11864
-
evgen@moonbone.local authored
into moonbone.local:/work/mysql-5.0-bug-10802
-
evgen@moonbone.local authored
into moonbone.local:/work/mysql-5.0-bug-11864
-
evgen@moonbone.local authored
HP-UX compiler was generating code which makes wrong conversion from double to ulonglong which results in not using index in some cases. Changed type cast operators odrer with which generated code makes proper conversion.
-
- 14 Aug, 2005 3 commits
-
-
serg@sergbook.mysql.com authored
-
serg@sergbook.mysql.com authored
into sergbook.mysql.com:/usr/home/serg/Abk/mysql-5.0
-
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 9 commits
-
-
sanja@hasky.mysql.fi authored
remove unneeded multitable_view assignment sql_view.cc: fix potential memorry overrun in ref_array asssign multitable_view in time of view creation (BUG#12569)
-
sanja@hasky.mysql.fi authored
into hasky.mysql.fi:/home/sanja/work-merge-5.0
-
sanja@hasky.mysql.fi authored
postmerge fix subselect.result: new 5.0 result (postmerge)
-
serg@sergbook.mysql.com authored
-
sanja@hasky.mysql.fi authored
into hasky.mysql.fi:/home/sanja/work-merge-5.0
-
bell@50.0.168.192.in-addr.arpa authored
into 50.0.168.192.in-addr.arpa:/Users/bell/mysql/bk/work-bug2-4.1
-
bell@50.0.168.192.in-addr.arpa authored
into 50.0.168.192.in-addr.arpa:/Users/bell/mysql/bk/work-bug2-4.1
-
bell@50.0.168.192.in-addr.arpa authored
-
tsmith@.mysql.com authored
Don't skip SET command even if --replicate-wild* says to. E.g., SET ONE_SHOT TIME_ZONE = 'XYZ' should be executed (BUG #12542)
-
- 12 Aug, 2005 19 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-4.1-merge
-
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
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com authored
Removed duplicate usage of TMP_TABLE_FORCE_MYISAM by making 'options' longlong
-
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.
-