An error occurred fetching the project authors.
- 16 Nov, 2006 1 commit
-
-
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.
-
- 01 Nov, 2006 1 commit
-
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-4.1-runtime
-
- 30 Oct, 2006 2 commits
-
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug21915
-
kroki/tomash@moonlight.intranet authored
If the user has specified --max-connections=N or --table-open-cache=M options to the server, a warning could be given that some values were recalculated, and table-open-cache could be assigned greater value. Note that both warning and increase of table-open-cache were totally harmless. This patch fixes recalculation code to ensure that table-open-cache will be never increased automatically and that a warning will be given only if some values had to be decreased due to operating system limits. No test case is provided because we neither can't predict nor control operating system limits for maximal number of open files.
-
- 27 Oct, 2006 4 commits
-
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
-
jonas@perch.ndb.mysql.com authored
Still leakage, make sure all unlinked operations are put back so they will be release (on failing blob operations, when AO_IgnoreError)
-
- 25 Oct, 2006 9 commits
-
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug18819
-
kroki/tomash@moonlight.intranet authored
If the error happens during DELETE IGNORE, nothing could be send to the client, thus leaving it frozen expecting the reply. The problem was that if some error occurred, it wouldn't be reported to the client because of IGNORE, but neither success would be reported. MySQL 4.1 would not freeze the client, but will report ERROR 1105 (HY000): Unknown error instead, which is also a bug. The solution is to report success if we are in DELETE IGNORE and some non-fatal error has happened.
-
mskold/marty@mysql.com/linux.site authored
into mysql.com:/windows/Linux_space/MySQL/mysql-4.1-ndb
-
mskold/marty@mysql.com/linux.site authored
into mysql.com:/windows/Linux_space/MySQL/mysql-4.1-ndb
-
mskold/marty@mysql.com/linux.site authored
Bug #21072 Duplicate key error in NDB references wrong key: Re-wrote string usage to avoid valgrind warnings
-
knielsen@ymer.(none) authored
into ymer.(none):/usr/local/mysql/mysql-4.1-ndb
-
knielsen@ymer.(none) authored
bugs.
-
stewart@willster.(none) authored
into willster.(none):/home/stewart/Documents/MySQL/4.1/bug19914-mk2-merge2
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
-
- 23 Oct, 2006 2 commits
-
-
stewart@willster.(none) authored
fixes for ndb_* tests broken by previous fix be more careful in ndb about setting errors on failure of info call (especially in open)
-
stewart@willster.(none) authored
into willster.(none):/home/stewart/Documents/MySQL/4.1/bug19914-mk2-merge2
-
- 20 Oct, 2006 4 commits
-
-
jonas@perch.ndb.mysql.com authored
Fix some too small buffers in backup
-
jonas@perch.ndb.mysql.com authored
Fixed a 4.1/5.0 vs. 5.1 name change in latest SR bug fix
-
jonas@perch.ndb.mysql.com authored
Fix monster SR bug making SR with ordered indexes (or temporary tables) broken
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data/bk/team_tree_merge/MERGE/mysql-4.1-opt
-
- 19 Oct, 2006 6 commits
-
-
mskold/marty@mysql.com/linux.site authored
into mysql.com:/windows/Linux_space/MySQL/mysql-4.1-ndb
-
mskold/marty@mysql.com/linux.site authored
Bug #21072 Duplicate key error in NDB references wrong key: use MAX_KEY to signal unknown key: Added string initialization
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/engines/mysql-4.1-engines
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data/bk/team_tree_merge/MERGE/mysql-4.1-opt
-
svoj@mysql.com/april.(none) authored
into mysql.com:/home/svoj/devel/mysql/engines/mysql-4.1-engines
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-merge
-
- 18 Oct, 2006 3 commits
-
-
jonas@perch.ndb.mysql.com authored
Make sure postExecute is not run for blobs if AO_IgnoreError
-
mskold/marty@mysql.com/linux.site authored
into mysql.com:/windows/Linux_space/MySQL/mysql-4.1-ndb
-
svoj@mysql.com/april.(none) authored
Repair table could crash a server if there is not sufficient memory (myisam_sort_buffer_size) to operate. Affects not only repair, but also all statements that use create index by sort: repair by sort, parallel repair, bulk insert. Return an error if there is not sufficient memory to store at least one key per BUFFPEK. Also fixed memory leak if thr_find_all_keys returns an error.
-
- 17 Oct, 2006 2 commits
-
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug21726
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-bug12240
-
- 16 Oct, 2006 3 commits
-
-
gkodinov/kgeorge@rakia.(none) authored
into rakia.(none):/home/kgeorge/mysql/autopush/B14019-4.1-opt
-
istruewing@chilla.local authored
into chilla.local:/home/mydev/mysql-4.1-bug12240
-
gkodinov/kgeorge@macbook.gmz authored
When resolving unqualified name references MySQL was not checking what is the item type for the reference. Thus e.g a string literal item that has by convention a name equal to its string value will also work as a reference to a SELECT list item or a table field. Fixed by allowing only Item_ref or Item_field to referenced by (unqualified) name.
-
- 13 Oct, 2006 2 commits
-
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug9678
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug9678
-
- 12 Oct, 2006 1 commit
-
-
jonas@perch.ndb.mysql.com authored
Fix race-condition between COPY_GCIREQ (GCP) and lcpSetActiveStatusEnd Solution is _not_ to copy sysfileData from COPY_GCIREQ from "self"
-