- 18 May, 2007 3 commits
-
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-ndb
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/50-work
-
jonas@perch.ndb.mysql.com authored
Make sure that data can not e left lingering in receive buffer
-
- 15 May, 2007 4 commits
-
-
tomas@whalegate.ndb.mysql.com authored
-
tomas@whalegate.ndb.mysql.com authored
-
tomas@whalegate.ndb.mysql.com authored
backported error code from 5.1 split error check when reading schema file
-
tomas@whalegate.ndb.mysql.com authored
- added errormessage and code for "declaring node dead"
-
- 14 May, 2007 4 commits
-
-
tomas@whalegate.ndb.mysql.com authored
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb
-
tomas@whalegate.ndb.mysql.com authored
- add retry sleep to allow temprary error to go away
-
mikael@dator3.(none) authored
into dator3.(none):/home/mikael/mysql_clones/rt-5.0
-
- 11 May, 2007 1 commit
-
-
tomas@whalegate.ndb.mysql.com authored
- make sure resources are release properly on error
-
- 10 May, 2007 4 commits
-
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb
-
mikael@dator3.(none) authored
into dator3.(none):/home/mikael/mysql_clones/rt-5.0
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-4.1-ndb
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb
-
- 09 May, 2007 4 commits
-
-
tomas@whalegate.ndb.mysql.com authored
enable setting api reg req frequency to be higher than heartbeat setting to ensure we have reasonably up-to-date info from ndb nodes + do this for management server
-
tomas@whalegate.ndb.mysql.com authored
- corrected previous patch - some platforms do strange things with char... use Int8 to be sure of signedness
-
evgen@moonbone.local authored
A test case is corrected.
-
tomas@whalegate.ndb.mysql.com authored
- some platforms do strange things with char... use Int8 to be sure of signedness
-
- 08 May, 2007 10 commits
-
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/27670-bug-5.0-opt-mysql
-
evgen@moonbone.local authored
TIMESTAMP field when no value has been provided. The LOAD DATA sets the current time in the TIMESTAMP field with CURRENT_TIMESTAMP default value when the field is detected as a null. But when the LOAD DATA command loads data from a file that doesn't contain enough data for all fields then the rest of fields are simply set to null without any check. This leads to no value being inserted to such TIMESTAMP field. Now the read_sep_field() and the read_fixed_length() functions set current time to the TIMESTAMP field with CURRENT_TIMESTAMP default value in all cases when a NULL value is loaded to the field.
-
tomas@whalegate.ndb.mysql.com authored
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-ndb
-
jonas@perch.ndb.mysql.com authored
redo extra verification code so that tupkeyref is reset just before tupkeyreq
-
mikron@mikael-ronstr-ms-dator.local authored
into mikael-ronstr-ms-dator.local:/Users/mikron/mysql_clones/mysql-5.0-ndb
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-ndb
-
jonas@perch.ndb.mysql.com authored
bug in interpretedupdate (used for auto-increment) that made TUPKEYREF be sent twice this was however "normally" shadowed, but made LQH crash when LCP was about to start
-
gni/root@dev3-221.dev.cn.tlan authored
into dev3-221.dev.cn.tlan:/home/ngb/mysql/mysql-4.1/mysql-4.1-ndb
-
gni@dev3-221.dev.cn.tlan authored
into dev3-221.dev.cn.tlan:/home/ngb/mysql/mysql-5.0/mysql-5.0-ndb
-
- 07 May, 2007 10 commits
-
-
igor@olga.mysql.com authored
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/27759-bug-5.0-opt-mysql
-
evgen@moonbone.local authored
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/mysql-5.0-opt-27954
-
gshchepa/uchum@gleb.loc authored
This bug affects multi-row INSERT ... ON DUPLICATE into table with PRIMARY KEY of AUTO_INCREMENT field and some additional UNIQUE indices. If the first row in multi-row INSERT contains duplicated values of UNIQUE indices, then following rows of multi-row INSERT (with either duplicated or unique key field values) may me applied to _arbitrary_ records of table as updates. This bug was introduced in 5.0. Related code was widely rewritten in 5.1, and 5.1 is already free of this problem. 4.1 was not affected too. When updating the row during INSERT ON DUPLICATE KEY UPDATE, we called restore_auto_increment(), which set next_insert_id back to 0, but we forgot to set clear_next_insert_id back to 0. restore_auto_increment() function has been fixed.
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/28133-bug-5.0-opt-mysql
-
evgen@moonbone.local authored
The IN function was comparing DATE/DATETIME values either as ints or as strings. Both methods have their disadvantages and may lead to a wrong result. Now IN function checks whether all of its arguments has the STRING result types and at least one of them is a DATE/DATETIME item. If so it uses either an object of the in_datetime class or an object of the cmp_item_datetime class to perform its work. If the IN() function arguments are rows then row columns are checked whether the DATE/DATETIME comparator should be used to compare them. The in_datetime class is used to find occurence of the item to be checked in the vector of the constant DATE/DATETIME values. The cmp_item_datetime class is used to compare items one by one in the DATE/DATETIME context. Both classes obtain values from items with help of the get_datetime_value() function and cache the left item if it is a constant one.
-
evgen@moonbone.local authored
Fixed compiler warnings.
-
mikron@mikael-ronstr-ms-dator.local authored
-
mikron@mikael-ronstr-ms-dator.local authored
-