mariadb

Tree: f6871c0d66

Author	SHA1	Message	Date
kaa@kaamos.(none)	8d222210c7	Fix for bug #31236 : Inconsistent division by zero behavior for floating point numbers Some math functions did not check if the result is a valid number (i.e. neither of +-inf or nan). Fixed by validating the result where necessary and returning NULL in case of invalid result.	18 years ago
kostja@dipika.(none)	812ee08488	Merge bk-internal.mysql.com:/home/bk/mysql-5.1-runtime into dipika.(none):/opt/local/work/mysql-5.1-runtime	18 years ago
kostja@dipika.(none)	f8ec5e0984	Fix a compilation failure of the community tree.	18 years ago
tomas@poseidon.bredbandsbolaget.se	50d95649f7	Merge tulin@bk-internal.mysql.com:/home/bk/mysql-5.1 into poseidon.bredbandsbolaget.se:/home/tomas/mysql-5.1-new-ndb-merge	18 years ago
guilhem@gbichot4.local	3fe6684c48	fixes for build failures due to my yesterday's changeset forbidding bool in C.	18 years ago
tsmith@ramayana.hindu.god	b8b6c7fcf7	Applied InnoDB snapshot innodb-5.1-ss2298 Fixes the following bugs: - Bug #33349: possible race condition revolving around data dictionary and repartitioning Introduce retry/sleep logic as a workaround for a transient bug where ::open fails for partitioned tables randomly if we are using one file per table. - Bug #34053: normal users can enable innodb_monitor logging In CREATE TABLE and DROP TABLE check whether the table in question is one of the magic innodb_monitor tables and whether the user has enough rights to mess with it before doing anything else. - Bug #22868: 'Thread thrashing' with > 50 concurrent conns under an upd-intensive workloadw - Bug #29560: InnoDB >= 5.0.30 hangs on adaptive hash rw-lock 'waiting for an X-lock' This is a combination of changes that forward port the scalability fix applied to 5.0 through r1001. It reverts changes r149 and r122 (these were 5.1 specific changes made in lieu of scalability fix of 5.0) Then it applies r1001 to 5.0 which is the original scalability fix. Finally it applies r2082 which fixes an issue with the original fix. - Bug #30930: Add auxiliary function to retrieve THD::thread_id Add thd_get_thread_id() function. Also make check_global_access() function visible to InnoDB under INNODB_COMPATIBILITY_HOOKS #define.	18 years ago
gkodinov/kgeorge@magare.gmz	5b508f2d16	Bug #30604 : different flagging of time_zone_used in normal and ps-protocol Finding a routine should be a transparent operation as far as the binary log is concerned. But it was influencing the binary log because of the TIMESTAMP column in the proc table. Fixed by preserving and restoring the time_zone usage flag when searching for a stored routine in the proc table.	18 years ago
davi@endora.local	d5847eb112	Merge bk-internal.mysql.com:/home/bk/mysql-5.1-runtime into mysql.com:/Users/davi/mysql/mysql-5.1-runtime	18 years ago
davi@endora.local	84a0d7c507	Merge mysql.com:/Users/davi/mysql/bugs/23771-5.1 into mysql.com:/Users/davi/mysql/mysql-5.1-runtime	18 years ago
vvaintroub@wva.	b609c158d8	Post-merge fix	18 years ago
vvaintroub@wva.	efa91b5479	Merge wva.:C:/bk/bug31745_2/my51_31754_2/..\my50-bug31745_2 into wva.:C:/bk/bug31745_2/my51_31754_2	18 years ago
kostja@dipika.(none)	72495c968b	Rename send_eof() to my_eof() for consistency with my_ok() and my_error()	18 years ago
kostja@dipika.(none)	f106d9738a	Rename send_ok to my_ok. Similarly to my_error, it only records the status, does not send it to the client.	18 years ago
kostja@dipika.(none)	d8e6308c42	Merge bk-internal.mysql.com:/home/bk/mysql-5.1-runtime into dipika.(none):/opt/local/work/mysql-5.1-2pc-opt-merge-push	18 years ago
kostja@dipika.(none)	acf9b1f346	A fix and a test case for Bug#12713 "Error in a stored function called from a SELECT doesn't cause ROLLBACK of statem". The idea of the fix is to ensure that we always commit the current statement at the end of dispatch_command(). In order to not issue redundant disc syncs, an optimization of the two-phase commit protocol is implemented to bypass the two phase commit if the transaction is read-only.	18 years ago
vvaintroub@wva.	f5932c0d95	Bug#31745 - crash handler does not work on Windows - Replace per-thread signal()'s with SetUnhandledExceptionFilter(). The only remaining signal() is for SIGABRT (default abort() handler in VS2005 is broken, i.e removes user exception filter) - remove MessageBox()'es from error handling code - Windows port for print_stacktrace() and write_core() - Cleanup, removed some unused functions	18 years ago
guilhem@gbichot4.local	045f3c4a5d	Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-5.1-build into gbichot4.local:/home/mysql_src/mysql-5.1-build-gca	18 years ago
guilhem@gbichot4.local	9e2b31b026	Fix for server bug experienced in Maria (wrong "Truncated incorrect <var_name> value" error even though the value was correct): a C function in my_getopt.c was taking bool* in parameter and was called from C++ sql_plugin.cc, but on some Mac OS X sizeof(bool) is 1 in C and 4 in C++, giving funny mismatches. Fixed, all other occurences of bool in C are removed, future ones are blocked by a "C-bool-catcher" in my_global.h (use my_bool).	18 years ago
tsmith@ramayana.hindu.god	a6d50c102c	Merge tsmith@bk-internal.mysql.com:/home/bk/mysql-5.1-build into ramayana.hindu.god:/home/tsmith/m/bk/build/51	18 years ago
tsmith@ramayana.hindu.god	732eb0b4ce	Merge ramayana.hindu.god:/home/tsmith/m/bk/build/50 into ramayana.hindu.god:/home/tsmith/m/bk/build/51	18 years ago
tsmith@ramayana.hindu.god	71faa39360	Merge ramayana.hindu.god:/home/tsmith/m/bk/50-b28555 into ramayana.hindu.god:/home/tsmith/m/bk/build/50	18 years ago
tsmith@ramayana.hindu.god	958f615f36	Merge ramayana.hindu.god:/home/tsmith/m/bk/b21158/50 into ramayana.hindu.god:/home/tsmith/m/bk/build/50	18 years ago
tsmith@ramayana.hindu.god	69dcac5a7e	Bug #28555 Upgrading MySQL Fails to shut down old server and kills socket file Check for an existing MySQL server package from a different vendor or major MySQL version. In such a case, refuse to install the server and recommend how to safely remove the old packages before installing the new ones.	18 years ago
tsmith@ramayana.hindu.god	845b94451f	Bug #28460 mysqlhotcopy silently skips a database with two alphanumerics name Remove code from mysqlhotcopy which deals with the so-called "RAID" feature of older MyISAM.	18 years ago
gkodinov/kgeorge@magare.gmz	ee33f13668	Merge gkodinov@bk-internal.mysql.com:/home/bk/mysql-5.1-opt into magare.gmz:/home/kgeorge/mysql/autopush/warnings-5.1-opt	18 years ago
gkodinov/kgeorge@magare.gmz	459ca66609	Fixed duplicate defition warning for bug 31887	18 years ago
holyfoot/hf@hfmain.(none)	0076314bde	Merge abotchkov@bk-internal.mysql.com:/home/bk/mysql-5.1-opt into mysql.com:/home/hf/work/32942/my51-32942	18 years ago
kent@kent-amd64.(none)	6761108f29	Merge mysql.com:/home/kent/bk/maria/mysql-maria-gca into mysql.com:/home/kent/bk/build/mysql-5.1-build	18 years ago
holyfoot/hf@hfmain.(none)	6f044073b8	Merge mysql.com:/home/hf/work/32942/my50-32942 into mysql.com:/home/hf/work/32942/my51-32942	18 years ago
holyfoot/hf@hfmain.(none)	652b7099ca	Merge bk@192.168.21.1:mysql-5.0-opt into mysql.com:/home/hf/work/32942/my50-32942	18 years ago
anozdrin/alik@quad.	f4659b38af	Merge quad.:/mnt/raid/alik/MySQL/devel/5.1 into quad.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged	18 years ago
anozdrin/alik@quad.	48058cf10b	Merge quad.:/mnt/raid/alik/MySQL/devel/5.0-rt into quad.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged	18 years ago
holyfoot/hf@hfmain.(none)	0c8df13cda	Merge bk@192.168.21.1:mysql-5.1-opt into mysql.com:/home/hf/work/32942/my51-32942	18 years ago
kent@mysql.com/kent-amd64.(none)	5d3d61f459	CMakeLists.txt: Missing "sql_profile.cc" was added	18 years ago
holyfoot/hf@hfmain.(none)	377ecd81c7	Merge mysql.com:/home/hf/work/32942/my50-32942 into mysql.com:/home/hf/work/32942/my51-32942	18 years ago
kaa@kaamos.(none)	93cbe28aac	Initialization order cleanups to get rid of warnings from the -Wreorder option added by the patch for bug#31326.	18 years ago
kaa@kaamos.(none)	1e6e9ca6fe	Merge kaamos.(none):/data/src/opt/mysql-5.0-opt into kaamos.(none):/data/src/opt/mysql-5.1-opt	18 years ago
kaa@kaamos.(none)	7e43bc00f2	Merge ssh://bk-internal.mysql.com//home/bk/mysql-5.1-opt into kaamos.(none):/data/src/opt/mysql-5.1-opt	18 years ago
kaa@kaamos.(none)	443c1a8b19	Merge ssh://bk-internal.mysql.com//home/bk/mysql-5.0-opt into kaamos.(none):/data/src/opt/mysql-5.0-opt	18 years ago
kaa@kaamos.(none)	3ef2f282bb	Merge kaamos.(none):/data/src/opt/mysql-5.0-opt into kaamos.(none):/data/src/opt/mysql-5.1-opt	18 years ago
kaa@kaamos.(none)	5671fb90e7	Post-merge fix.	18 years ago
kaa@kaamos.(none)	5647dee192	Merge kaamos.(none):/data/src/mysql-5.1 into kaamos.(none):/data/src/opt/mysql-5.1-opt	18 years ago
holyfoot/hf@mysql.com/hfmain.(none)	7abba3b021	Bug #32942 now() - interval '7200' second NOT pre-calculated, causing "full table scan" Problem is not about intervals and doesn't actually cause 'full table scan'. We have an optimization for DISTINCT when we have 'DISTINCT field_from_first_join_table' we don't need to read all the rows from the JOIN-ed table if we found one conforming row. It stopped working in 5.0 as we return NESTED_LOOP_OK if we came upon that case in the evaluate_join_record() and that doesn't break the recordreading loop in sub_select(). Fixed by returning NESTED_LOOP_NO_MORE_ROWS in this case.	18 years ago
kaa@kaamos.(none)	cb80b23e23	Merge kaamos.(none):/data/src/opt/mysql-4.1-opt into kaamos.(none):/data/src/opt/mysql-5.0-opt	18 years ago
kaa@kaamos.(none)	3daeb40f1f	Merge kaamos.(none):/data/src/mysql-5.0 into kaamos.(none):/data/src/opt/mysql-5.0-opt	18 years ago
kaa@kaamos.(none)	7b9dce58d9	Merge kaamos.(none):/data/src/mysql-4.1 into kaamos.(none):/data/src/opt/mysql-4.1-opt	18 years ago
gkodinov/kgeorge@magare.gmz	88af101d44	merge of bug 31887 5.0-opt->5.1-opt	18 years ago
gkodinov/kgeorge@magare.gmz	047b1a66a0	Merge magare.gmz:/home/kgeorge/mysql/work/B31887-5.0-opt into magare.gmz:/home/kgeorge/mysql/work/B31887-5.1-opt	18 years ago
gkodinov/kgeorge@magare.gmz	a781c1b140	Merge gkodinov@bk-internal.mysql.com:/home/bk/mysql-5.0-opt into magare.gmz:/home/kgeorge/mysql/autopush/B31887-5.0-opt	18 years ago
gkodinov/kgeorge@magare.gmz	490ec62be4	Bug #31887 : DML Select statement not returning same results when executed in version 5 Zero fill is a field attribute only. So we can't always propagate constants for zerofill fields : the values and expression results don't have that flag. Fixed by converting the const value to a string and using that in const propagation when the context allows it. Disable const propagation for fields with ZEROFILL flag in all the other cases.	18 years ago

... 3 4 5 6 7 ...

53265 Commits (f6871c0d661d1d6be814cc539bd33d5bf1a243d2) All Branches Search

53265 Commits (f6871c0d661d1d6be814cc539bd33d5bf1a243d2)

All Branches