- 15 Nov, 2006 2 commits
-
-
into salvation.intern.azundris.com:/home/tnurnberg/work/mysql-5.1-maint-16456
-
calling (rather than defining) non-deterministic SP in SBR (as opposed to RBR or mixed) will throw an error now. require mixed mode for tests now. SBR will now fail when calling non-deter SPs and SFs (as it should), and RBR already failed by virtue of giving different results for "show binlog" than the results-file has. also test for 16456 now. lastly make amends because one of the tests fails with a new error # now as code was added to sql_trigger.cc while test was disabled.
-
- 14 Nov, 2006 1 commit
-
-
kaa@polly.local authored
into polly.local:/home/kaa/src/maint/mysql-5.1-maint
-
- 13 Nov, 2006 15 commits
-
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-maint
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug18761/my51-bug18761
-
cmiller@zippy.cornsilk.net authored
The code that set up data to be passed to user-defined functions was very old and analyzed the "Type" of the data that was passed into the UDF, when it really should analyze the "return_type", which is hard-coded for simple Items and works correctly for complex ones like functions. --- Added test at Sergei's behest.
-
guilhem@gbichot3.local authored
in Makefile.am.
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@neptunus.(none) authored
Add new test file mysql_upgrade.test
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
msvensson@neptunus.(none) authored
- Cleanup the Makefile for client - Don't link mysqltest with mysys as it's been compiled with different flags.
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
use MTR_MEM environment variable
-
- 11 Nov, 2006 3 commits
-
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-maint
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug22860/my51-bug22860
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug22860/my50-bug22860
-
- 10 Nov, 2006 13 commits
-
-
cmiller@zippy.cornsilk.net authored
Support says that memlock doesn't work on OSes other than Solaris. Add a warning about --memlock to the crash monologue.
-
iggy@rolltop.ignatz42.dyndns.org authored
into rolltop.ignatz42.dyndns.org:/mnt/storeage/mtr_winfix/my51-mtr_winfix
-
iggy@rolltop.ignatz42.dyndns.org authored
into rolltop.ignatz42.dyndns.org:/mnt/storeage/mtr_winfix/my50-mtr_winfix
-
iggy@rolltop.ignatz42.dyndns.org authored
Test Suite failing on Windows because the $opt_report_features variable was not defined before use.
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-maint
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-maint
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug20691/my51-bug20691
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
Improve log message
-
ted@ted.mysql.internal authored
into ted.mysql.internal:/home/ted/src/mysql/mysql-5.1-new-maint
-
ted@ted.mysql.internal authored
-
- 09 Nov, 2006 6 commits
-
-
cmiller@zippy.cornsilk.net authored
specifying DEFAULT This was not specific to datetime. When there is no default value for a column, and the user inserted DEFAULT, we would write uninitialized memory to the table. Now, insist on writing a default value, a zero-ish value, the same one that comes from inserting NULL into a not-NULL field. (This is, at best, really strange behavior that comes from allowing sloppy usage, and serves as a good reason always to run one's server in a strict SQL mode.)
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@neptunus.(none) authored
-