- 30 Jun, 2005 1 commit
-
-
lenz@mysql.com authored
"changed dl_name to udf->dl in mysql_create_function"
-
- 23 Jun, 2005 1 commit
-
-
lenz@mysql.com authored
-
- 08 Jun, 2005 1 commit
-
-
svoj@mysql.com authored
BUG#10675 - MySQL fails to build with --openssl on Mac OS X 10.4 BUG#11150 - HP-UX yaSSL/OpenSSL configure/header problem Remove obsolete code.
-
- 06 Jun, 2005 1 commit
-
-
mronstrom@mysql.com authored
into mysql.com:/Users/mikron/bug10901
-
- 03 Jun, 2005 5 commits
-
-
mronstrom@mysql.com authored
After review fix Copy from internal state to share state only when in lock write mode (happens only when lock table x write has been performed since update_state_info is only called when holding a TL_READ_NO_INSERT lock normally. Previous patch would have failed in combination with delayed writes.
-
mronstrom@mysql.com authored
Analyze table corrupts the state on data_file_length, records, index_file_length... by writing the shared state when there is an updated internal state due to inserts or deletes Fixed by synching the shared state with the internal state before writing it to disk Added test cases of 2 error cases and a normal case in new analyze test case
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
and HAVE_ATOMIC_ADD/HAVE_ATOMIC_SUB is tested in configure
-
ndbdev@dl145b.mysql.com authored
Bug #11064 some read error not detected in replication on 64-bit platform
-
- 01 Jun, 2005 1 commit
-
-
lenz@mysql.com authored
- removed obsolete mysql-max.spec.sc RPM spec file (Max is built out of the standard spec file)
-
- 31 May, 2005 1 commit
-
-
ingo@mysql.com authored
1.) Added a new option to mysql_lock_tables() for ignoring FLUSH TABLES. Used the new option in create_table_from_items(). It is necessary to prevent the SELECT table from being reopend. It would get new storage assigned for its fields, while the SELECT part of the command would still use the old (freed) storage. 2.) Protected the CREATE TABLE and CREATE TABLE ... SELECT commands against a global read lock. This prevents a deadlock in CREATE TABLE ... SELECT in conjunction with FLUSH TABLES WITH READ LOCK and avoids the creation of new tables during a global read lock. 3.) Replaced set_protect_against_global_read_lock() and unset_protect_against_global_read_lock() by wait_if_global_read_lock() and start_waiting_global_read_lock() in the INSERT DELAYED handling.
-
- 26 May, 2005 2 commits
-
-
joerg@mysql.com authored
into mysql.com:/M40/mysql-4.0
-
marko@hundin.mysql.fi authored
-
- 25 May, 2005 1 commit
-
-
joerg@mysql.com authored
Added a missing "make clean" to the RPM "spec" file which had caused the original 4.1.12 RPMs to be broken. (bug#10674, bug#10681)
-
- 18 May, 2005 2 commits
-
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mylan authored
when reporting an error, use an appropriate buffer for udf->name
-
- 15 May, 2005 2 commits
-
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-4.0-bug10095
-
sergefp@mysql.com authored
The problem: base_list::remove didn't modify base_list::last when removing the last list element. The fix: If we remove the last element, find the element before it (by walking from the beginning of the list) and set base_list::last accordingly. The list gets corrupted in both 4.0 and 4.1. There are no visible problems in current 4.1 because current 4.1 doesn't call where_cond->fix_fields() after constant propagation step.
-
- 14 May, 2005 1 commit
-
-
monty@mysql.com authored
-
- 13 May, 2005 2 commits
-
-
monty@mysql.com authored
Fixed wrong buffer usage for auto-increment key with blob part that caused CHECK TABLE to report that the table was wrong. (Bug #10045)
-
monty@mysql.com authored
Count null_bits separately from field offsets and adjust them in case of primary key parts. (Previously a CREATE TABLE with a lot of null fields that was part of a primary key caused MySQL to wrongly count the number of bytes needed to store null bits) This is a more complete bug fix for #6236
-
- 11 May, 2005 1 commit
-
-
paul@kite-hub.kitebird.com authored
Remove obsolete section number. (Bug #10534)
-
- 09 May, 2005 1 commit
-
-
antony@ltantony.mysql.com authored
-
- 08 May, 2005 4 commits
-
-
antony@ltantony.mysql.com authored
into ltantony.mysql.com:/usr/home/antony/work2/megapatch-4.0
-
antony@ltantony.mysql.com authored
into ltantony.mysql.com:/usr/home/antony/work2/megapatch-4.0
-
antony@ltantony.mysql.com authored
Fix bug + include test case. Enable outfile tests.
-
antony@ltantony.mysql.com authored
Incomplete ALTER TABLE breaks MERGE compatibility Fix implicit NOT NULL not set on ALTER of PK columns
-
- 07 May, 2005 8 commits
-
-
mwagner@ultrafly.mysql.com authored
into ultrafly.mysql.com:/Users/mwagner/work/bk/mysql-4.0
-
svoj@mysql.com authored
into mysql.com:/home/svoj/devel/mysql/7709-mysql-4.0
-
svoj@mysql.com authored
-
jimw@mysql.com authored
-
mwagner@ultrafly.mysql.com authored
Add newline at EOF for proper processing by comp-err.exe on Windows where fgets() works differently than Linux (Bug #6195).
-
svoj@mysql.com authored
fail.
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0
-
gbichot@production.mysql.com authored
when merging just use "ul"] In configure.in, don't remove $AVAILABLE_LANGUAGES_ERRORS_RULES at end because config.status may later need this file (if it does not find it it won't incorporate dependencies of errmsg.sys in sql/share/Makefile). In sql/share/Makefile.am using "all:" leads to double-"all:" in Makefile.
-
- 06 May, 2005 3 commits
-
-
lenz@mysql.com authored
-
lenz@mysql.com authored
- added some required CXXFLAGS to BUILD/compile-dist to allow the distribution build to pass without unresolved symbols
-
antony@ltantony.mysql.com authored
MySQL server 100% CPU if FLUSH TABLES WITH READ LOCK + INSERT Infinite loop caused by missing update to thd version.
-
- 29 Apr, 2005 1 commit
-
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.0-clean
-
- 28 Apr, 2005 1 commit
-
-
ingo@mysql.com authored
This is the second of three changesets. It contains the pure bug fix. It also contains the second after-review fixes. The problem was that with gcc on x86, shifts are done modulo word size. 'value' is 32 bits wide and shifting it by 32 bits is a no-op. This was triggered by an evil distribution of character incidences. A distribution of 2917027827 characters made of 202 distinct values led to 34 occurrences of 32-bit Huffman codes. This might have been the first time ever that write_bits() had to write 32-bit values. Since it can be expected that one day even 32 bits might be insufficient, the third changeset suggests to enlarge some variables to 64 bits.
-