- 07 Dec, 2006 1 commit
-
-
svoj@mysql.com/april.(none) authored
table ROW_FORMAT option is lost during CREATE/DROP INDEX. This fix forces CREATE/DROP INDEX to retain ROW_FORMAT by instructing mysql_alter_table() that ROW_FORMAT is not used during creating/dropping indexes.
-
- 01 Dec, 2006 2 commits
-
-
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
-
- 30 Nov, 2006 1 commit
-
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-4.1-opt
-
- 29 Nov, 2006 7 commits
-
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-4.1-runtime
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-bug23139
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-4.1-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-4.1-opt
-
df@kahlann.erinye.com authored
into kahlann.erinye.com:/home/df/mysql/build/mysql-4.1-build-work
-
df@kahlann.erinye.com authored
-
holyfoot/hf@mysql.com/deer.(none) authored
the problem is that client tools are compiled with UNDEF_THREADS_HACK flag, and my thread-related additions to the mysqltest.c can't be compiled. Easy solution is to disable these in not-embedded case completely.
-
- 28 Nov, 2006 3 commits
-
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-4.1-runtime
-
kent@mysql.com/kent-amd64.(none) authored
If using \$(srcdir)/mysql.info in action, use same in rule.
-
istruewing@chilla.local authored
A corrupted compressed table could crash the server and myisamchk. The data file of an uncompressed table contains just the records. There is no header in the data file. However the data file of a compressed table has a header. The header describes how the table was compressed. This information is necessary to extract the records from the compressed data file. Part of the compressed data file header are the [de]code tables. They are numeric representations of the Huffman trees used for coding and decoding. A Huffman tree is a binary tree. Every node has two childs. A child can be a leaf or a branch. Leaves contain the decoded value. Branches point to another tree node. Since the [de]code table is represented as an array of childs, the branches need to point at a child within the same array. The corruption of the compressed data file from the bug report was a couple of branches that pointed outside their array. This condition had not been correctly checked. I added some checks for the pointers in the decode tables. This type of corruption will no longer crash the server or myisamchk. No test case. A corrupted compressed table is required.
-
- 27 Nov, 2006 3 commits
-
-
kent@mysql.com/kent-amd64.(none) authored
into mysql.com:/home/kent/bk/mysql-4.1-merge
-
kent@mysql.com/kent-amd64.(none) authored
BSD compatibility
-
kent@mysql.com/kent-amd64.(none) authored
Fix undefined behaviour. Many files: Reenabled build outside ource tree
-
- 24 Nov, 2006 1 commit
-
-
df@kahlann.erinye.com authored
-
- 22 Nov, 2006 3 commits
-
-
kroki/tomash@moonlight.intranet authored
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug21635
-
kroki/tomash@moonlight.intranet authored
expression cols. The problem was that MYSQL_FIELD::org_name was set for MIN() and MAX() functions (COUNT() is also mentioned in the bug report but was already fixed). After this patch for expressions MYSQL_FIELD::name is set to either expression itself or its alias, and other data origin fields of MYSQL_FILED (db, org_table, table, org_name) are empty strings.
-
- 21 Nov, 2006 2 commits
-
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug23159
-
kroki/tomash@moonlight.intranet authored
Make Prepared_stmt_count a global status variable, accessible via SHOW STATUS LIKE 'Prepared_stmt_count';. Documentation should be updated.
-
- 17 Nov, 2006 4 commits
-
-
dfischer/df@kahlann.erinye.com authored
-
holyfoot/hf@mysql.com/deer.(none) authored
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug23383
-
kroki/tomash@moonlight.intranet authored
mysql_stmt_affected_rows() The problem was that affected_rows for prepared statement wasn't updated in the client library on the error. The solution is to always update affected_rows, which will be equal to -1 on the error.
-
- 16 Nov, 2006 7 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M41/push-4.1
-
holyfoot/hf@mysql.com/deer.(none) authored
-
holyfoot/hf@mysql.com/deer.(none) authored
-
holyfoot/hf@mysql.com/deer.(none) authored
into mysql.com:/home/hf/work/mysql-4.1-mrg
-
joerg@trift2. authored
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug17047
-
kroki/tomash@moonlight.intranet authored
The problem was that some functions (namely IN() starting with 4.1, and CHAR() starting with 5.0) were returning NULL in certain conditions, while they didn't set their maybe_null flag. Because of that there could be some problems with 'IS NULL' check, and statements that depend on the function value domain, like CREATE TABLE t1 SELECT 1 IN (2, NULL);. The fix is to set maybe_null correctly.
-
- 15 Nov, 2006 4 commits
-
-
joerg@trift2. authored
-
lars@mysql.com/black.(none) authored
into mysql.com:/home/bk/MERGE/mysql-4.1-merge
-
mending windows test.
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-axmrg
-
- 14 Nov, 2006 2 commits
-
-
df@kahlann.erinye.com authored
-
df@kahlann.erinye.com authored
-