- 03 Sep, 2006 2 commits
-
-
jonas@perch.ndb.mysql.com authored
fix ndb-violations of strict aliasing found by gcc4.1 (crashes in ndb_dd_*)
-
jonas@perch.ndb.mysql.com authored
gcc-4.1.1 work-around for bug in strict-aliasing
-
- 31 Aug, 2006 3 commits
-
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime-merge
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1
-
- 30 Aug, 2006 2 commits
-
-
kostja@bodhi.local authored
-
georg@lmy002.wdf.sap.corp authored
CMake versions > 2.4 allow linking to STATIC or SHARED libraries only.
-
- 29 Aug, 2006 12 commits
-
-
kostja@bodhi.local authored
into bodhi.local:/opt/local/work/mysql-5.1-runtime-merge
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb
-
kostja@bodhi.local authored
doesn't find the column" When a user was using 4.1 tables with VARCHAR column and 5.0 server and a query that used a temporary table to resolve itself, the table metadata for the varchar column sent to client was incorrect: MYSQL_FIELD::table member was empty. The bug was caused by implicit "upgrade" from old VARCHAR to new VARCHAR hard-coded in Field::new_field, which did not preserve the information about the original table. Thus, the field metadata of the "upgraded" field pointed to an auxiliary temporary table created for query execution. The fix is to copy the pointer to the original table to the new field.
-
timour/timka@lamia.home authored
into lamia.home:/home/timka/mysql/src/5.1-bug-21456
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug17591
-
anozdrin/alik@alik. authored
- BUG#15934: Instance manager fails to work; - BUG#18020: IM connect problem; - BUG#18027: IM: Server_ID differs; - BUG#18033: IM: Server_ID not reported; - BUG#21331: Instance Manager: Connect problems in tests; The only test suite has been changed (server codebase has not been modified).
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug17591
-
kroki/tomash@moonlight.intranet authored
When a view was used inside a trigger or a function, lock type for tables used in a view was always set to READ (thus making the view non-updatable), even if we were trying to update the view. The solution is to set lock type properly.
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb
-
jonas@perch.ndb.mysql.com authored
Add order by in rpl_(ndb)_multi_update3 to make result deterministic
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb
-
jonas@perch.ndb.mysql.com authored
fix backup/lcp race
-
- 28 Aug, 2006 5 commits
-
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb
-
jonas@perch.ndb.mysql.com authored
Snapup testBackup XXXerror
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/51-work
-
jonas@perch.ndb.mysql.com authored
Improve error message when detecting corrupted REDO log
-
jonas@perch.ndb.mysql.com authored
adopt to new error code 755 (invalid tablespace)
-
- 25 Aug, 2006 12 commits
-
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/arch-5.1
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/arch-5.1
-
brian@zim.(none) authored
Fixed "discover" in the handler API. Fixed problem where handlerton was not zero'ed. I need to look around, I suspect this problem is more widespread.
-
andrey@example.com authored
into example.com:/work/mysql-5.0-runtime
-
jonas@perch.ndb.mysql.com authored
-
andrey@example.com authored
erroneous check Problem: Actually there were two problems in the server code. The check for SQLCOM_FLUSH in SF/Triggers were not according to the existing architecture which uses sp_get_flags_for_command() from sp_head.cc . This function was also missing a check for SQLCOM_FLUSH which has a problem combined with prelocking. This changeset fixes both of these deficiencies as well as the erroneous check in sp_head::is_not_allowed_in_function() which was a copy&paste error.
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb
-
anozdrin/alik@alik. authored
into alik.:/mnt/raid/alik/MySQL/devel/5.0-rt-bug16899
-
-
kroki/tomash@moonlight.intranet authored
-
jonas@perch.ndb.mysql.com authored
disable ndb_autodiscover3 (cluster restart (--initial))
-
-
- 24 Aug, 2006 4 commits
-
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb
-
jonas@perch.ndb.mysql.com authored
disable ndb_binlog_discover as it's broken remove debug printout
-
andrey@example.com authored
The following procedure was not possible if max_sp_recursion_depth is 0 create procedure show_proc() show create procedure show_proc; Actually there is no recursive call but the limit is checked. Solved by temporarily increasing the thread's limit just before the fetch from cache and decreasing after that.
-
anozdrin/alik@alik. authored
Changed trigger-handling code so that there will be the one place for generate statement string for replication log and for trigger file.
-