- 19 Mar, 2007 1 commit
-
-
istruewing@chilla.local authored
Using a MEMORY table BTREE index for scanning for updatable rows could lead to an infinite loop. Everytime a key was inserted into a btree index, the position in the index scan was cleared. The search started from the beginning and found the same key again. Now we do not clear the position on key insert an more.
-
- 05 Mar, 2007 1 commit
-
-
istruewing@chilla.local authored
Using INSERT DELAYED on MERGE tables could lead to table corruptions. The manual lists a couple of storage engines, which can be used with INSERT DELAYED. MERGE is not in this list. The attempt to try it anyway has not been rejected yet. This bug was not detected earlier as it can work under special circumstances. Most notable is low concurrency. To be safe, this patch rejects any attempt to use INSERT DELAYED on MERGE tables.
-
- 13 Feb, 2007 2 commits
-
-
ibabaev@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-4.1-opt
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-4.1-maint
-
- 12 Feb, 2007 4 commits
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
into mysql.com:/home/hf/work/25492/my41-25492
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
tnurnberg@mysql.com/sin.azundris.com authored
into mysql.com:/home/tnurnberg/24660/41-24660
-
tnurnberg@mysql.com/sin.azundris.com authored
ENUMs weren't allowed to have character 0xff, a perfectly good character in some locales. This was circumvented by mapping 0xff in ENUMs to ',', thereby prevent actual commas from being used. Now if 0xff makes an appearance, we find a character not used in the enum and use that as a separator. If no such character exists, we throw an error. Any solution would have broken some sort of existing behaviour. This solution should serve both fractions (those with 0xff and those with ',' in their enums), but WILL REQUIRE A DUMP/RESTORE CYCLE FROM THOSE WITH 0xff IN THEIR ENUMS. :-/ That is, mysqldump with their current server, and restore when upgrading to one with this patch.
-
- 08 Feb, 2007 2 commits
-
-
tsmith@siva.hindu.god authored
into siva.hindu.god:/home/tsmith/m/bk/maint/41
-
gluh@mysql.com/eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/4.1-opt
-
- 07 Feb, 2007 1 commit
-
-
tomas@poseidon.mysql.com authored
into poseidon.mysql.com:/home/tomas/mysql-4.1-ndb
-
- 06 Feb, 2007 8 commits
-
-
msvensson@pilot.mysql.com authored
into pilot.mysql.com:/home/msvensson/mysql/mysql-4.1-maint
-
msvensson@neptunus.(none) authored
- strerror might return NULL on some platforms
-
msvensson@pilot.mysql.com authored
into pilot.mysql.com:/home/msvensson/mysql/mysql-4.1-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
-
msvensson@pilot.mysql.com authored
into pilot.mysql.com:/home/msvensson/mysql/mysql-4.1-maint
-
msvensson@pilot.mysql.com authored
into pilot.mysql.com:/home/msvensson/mysql/mysql-4.1-maint
-
msvensson@neptunus.(none) authored
- Backport fix from 5.0
-
into mysql.com:/usr/home/ram/work/bug23938/my41-bug23938
-
- 05 Feb, 2007 2 commits
-
-
-
into mysql.com:/usr/home/ram/work/bug10798/my41-bug10798
-
- 02 Feb, 2007 5 commits
-
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-axmrg
-
istruewing@chilla.local authored
-
gluh@mysql.com/eagle.(none) authored
-
gluh@mysql.com/eagle.(none) authored
added valgrind.supp to EXTRA_SCRIPTS(for pushbuild)
-
istruewing@chilla.local authored
-
- 01 Feb, 2007 7 commits
-
-
into mysql.com:/home/ram/work/b26012/b26012.4.1
-
As we have Field_double::not_fixed we must have Field_double::size_of().
-
lzhou/zhl@dev3-63.(none) authored
into dev3-63.(none):/home/zhl/mysql/tree-merge/4.1/mysql-4.1-ndb
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-axmrg
-
gluh@mysql.com/eagle.(none) authored
Notes: This patch doesn't fix all issues in the tree and we need jani's fix for that This patch shoud not be merged into 5.0
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-axmrg
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-axmrg
-
- 31 Jan, 2007 7 commits
-
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-4.1-maint
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-4.1-maint
-
mtaylor@qualinost.(none) authored
into qualinost.(none):/home/mtaylor/src/mysql-4.1-maint
-
svoj@mysql.com/june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/WL3567/mysql-4.1-engines
-
svoj@mysql.com/june.mysql.com authored
When a merge table is opened compare column and key definition of underlying tables against column and key definition of merge table. If any of underlying tables have different column/key definition refuse to open merge table.
-
into mysql.com:/home/ram/work/b19690/b19690.4.1
-
Depending on the queries we use different data processing methods and can lose some data in case of double (and decimal in 4.1) fields. The fix consists of two parts: 1. double comparison changed, now double a is equal to double b if (a-b) is less than 5*0.1^(1 + max(a->decimals, b->decimals)). For example, if a->decimals==1, b->decimals==2, a==b if (a-b)<0.005 2. if we use a temporary table, store double values there as is to avoid any data conversion (rounding).
-