An error occurred fetching the project authors.
- 19 Feb, 2008 1 commit
-
-
davi@endora.local authored
into mysql.com:/Users/davi/mysql/mysql-5.1-runtime
-
- 18 Feb, 2008 2 commits
-
-
anozdrin/alik@quad. authored
into quad.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged
-
anozdrin/alik@quad. authored
into quad.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged
-
- 15 Feb, 2008 2 commits
-
-
anozdrin/alik@quad. authored
FK definition.
-
mkindahl@dl145h.mysql.com authored
failing on heavily loaded systems.
-
- 14 Feb, 2008 3 commits
-
-
anozdrin/alik@quad. authored
two timestamp fields. The actual problem here was that CREATE TABLE allowed zero date as a default value for a TIMESTAMP column in NO_ZERO_DATE mode. The thing is that for TIMESTAMP date type specific rule is applied: column_name TIMESTAMP == column_name TIMESTAMP DEFAULT 0 whever for any other date data type column_name TYPE == column_name TYPE DEFAULT NULL The fix is to raise an error when we're in NO_ZERO_DATE mode and there is TIMESTAMP column w/o default value.
-
mkindahl@dl145h.mysql.com authored
-
mkindahl@dl145h.mysql.com authored
BUG#24387, which is closed since long.
-
- 13 Feb, 2008 4 commits
-
-
mkindahl@dl145h.mysql.com authored
-
mkindahl@dl145h.mysql.com authored
irrelevant to execute since the charset information does not affect replication for row-based replication. The row-based versions of the tests were removed, and the statement-based version of the test was made executable by all three modes. This involves removing any lines that causes the test to be dependent on the contents of the binary log, and instead we just check that the replication works as it should.
-
anozdrin/alik@quad. authored
behave randomly with mysql_change_user. The test case had to be moved into not_embedded_server.test file, because SHOW GLOBAL STATUS does not work properly in embedded server (see bug 34517).
-
anozdrin/alik@quad. authored
-
- 12 Feb, 2008 5 commits
-
-
anozdrin/alik@quad. authored
but not collation. The problem here was that text literals in a view were always dumped with character set introducer. That lead to loosing collation information. The fix is to dump character set introducer only if it was in the original query. That is now possible because there is no problem any more of loss of character set of string literals in views -- after WL#4052 the view is dumped in the original character set.
-
anozdrin/alik@quad. authored
-
anozdrin/alik@quad. authored
behave randomly with mysql_change_user. The problem was that global status variables were not updated in THD::check_user(), so thread statistics were lost after COM_CHANGE_USER. The fix is to update global status variables with the thread ones before preparing the thread for new user.
-
mkindahl@dl145h.mysql.com authored
tree with main.
-
davi@mysql.com/endora.local authored
The problem is that AFTER UPDATE triggers will fire only if the new data is different from the old data on the row. The trigger should fire regardless of whether there are changes to the data. The solution is to fire the trigger on UPDATE even if there are no changes to the value (because the value is the same).
-
- 11 Feb, 2008 9 commits
-
-
mkindahl@dl145h.mysql.com authored
into dl145h.mysql.com:/data0/mkindahl/mysql-5.1-rpl-merge
-
mkindahl@dl145h.mysql.com authored
into dl145h.mysql.com:/data0/mkindahl/mysql-5.1-rpl-merge
-
mkindahl@dl145h.mysql.com authored
into dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl-merge
-
mkindahl@dl145h.mysql.com authored
into dl145h.mysql.com:/data0/mkindahl/mysql-5.1
-
anozdrin/alik@quad. authored
-
anozdrin/alik@quad. authored
(originally from Mats)
-
anozdrin/alik@quad. authored
(originally from Mats)
-
mkindahl@dl145h.mysql.com authored
into dl145h.mysql.com:/data0/mkindahl/mysql-5.1-rpl-merge
-
mkindahl@dl145h.mysql.com authored
into dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl-merge
-
- 09 Feb, 2008 4 commits
-
-
sven@riska.(none) authored
because it uses BINLOG statement, which is not supported in embedded mode. Fix: disable the test in embedded mode.
-
kostja@dipika.(none) authored
into dipika.(none):/opt/local/work/mysql-5.1-runtime
-
kostja@dipika.(none) authored
-
malff@lambda.hsd1.co.comcast.net. authored
-
- 08 Feb, 2008 10 commits
-
-
sven@riska.(none) authored
Problem: mysqlbinlog does not free memory if an error happens. Fix: binlog-processing functions do not call exit() anymore. Instead, they print an error and return an error code. Error codes are propagated all the way back to main, and all allocated memory is freed on the way.
-
anozdrin/alik@quad. authored
Disable the test case.
-
anozdrin/alik@quad. authored
-
kostja@dipika.(none) authored
-
kostja@dipika.(none) authored
into dipika.(none):/opt/local/work/mysql-5.1-runtime
-
kostja@dipika.(none) authored
into dipika.(none):/opt/local/work/mysql-5.1-runtime
-
kostja@dipika.(none) authored
into dipika.(none):/opt/local/work/mysql-5.0-runtime
-
kostja@dipika.(none) authored
simply killed.
-
kostja@dipika.(none) authored
into dipika.(none):/opt/local/work/mysql-5.1-runtime
-
kostja@dipika.(none) authored
-