- 05 Mar, 2008 3 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
- 03 Mar, 2008 4 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M51/mysql-5.1
-
joerg@trift2. authored
-
hhunger@hh-nb.hungers authored
-
anozdrin/alik@quad. authored
into quad.:/mnt/raid/alik/MySQL/devel/5.1-rt
-
- 29 Feb, 2008 4 commits
-
-
davi@endora.local authored
into mysql.com:/Users/davi/mysql/mysql-5.1-runtime
-
anozdrin/alik@quad. authored
READ_ONLY token was accidentally placed into wrong place ('ident' rule). The proper place is in the 'keyword_sp' rule. The manual should be re-generated after this patch, because the manual depends on the 'keyword_sp' rule.
-
iggy@alf.(none) authored
into alf.(none):/src/macro_bugs/my51-macro_bugs
-
iggy@alf.(none) authored
- Mistaken macro defintions cause mysys to read packets in the wrong order.
-
- 28 Feb, 2008 9 commits
-
-
davi@buzz.(none) authored
into buzz.(none):/home/davi/mysql-5.1-runtime
-
davi@mysql.com/endora.local authored
must match the order which they were declared in the class definition.
-
iggy@alf.(none) authored
into alf.(none):/src/macro_bugs/my51-macro_bugs
-
iggy@alf.(none) authored
into alf.(none):/src/macro_bugs/my50-macro_bugs
-
iggy@alf.(none) authored
into alf.(none):/src/macro_bugs/my51-macro_bugs
-
davi@mysql.com/endora.local authored
Rename client_last_error to last_error and client_last_errno to last_errno to not break connectors which use the internal net structure for error handling.
-
davi@mysql.com/endora.local authored
The problem is that passing anything other than a integer to a limit clause in a prepared statement would fail. This limitation was introduced to avoid replication problems (e.g: replicating the statement with a string argument would cause a parse failure in the slave). The solution is to convert arguments to the limit clause to a integer value and use this converted value when persisting the query to the log.
-
anozdrin/alik@quad. authored
sporadically.
-
anozdrin/alik@quad. authored
(show_check.test fails sporadically). Fix test case for Bug#12183 to make it stable.
-
- 27 Feb, 2008 9 commits
-
-
iggy@alf.(none) authored
into alf.(none):/src/macro_bugs/my51-macro_bugs
-
iggy@alf.(none) authored
- Remove duplicate macro defintions.
-
davi@endora.local authored
into mysql.com:/Users/davi/mysql/mysql-5.1-runtime
-
davi@mysql.com/endora.local authored
to reach the desired value.
-
anozdrin/alik@quad. authored
into quad.:/mnt/raid/alik/MySQL/devel/5.1-rt-build
-
anozdrin/alik@quad. authored
-
anozdrin/alik@quad. authored
-
davi@mysql.com/endora.local authored
Disable the test case.
-
kostja@dipika.(none) authored
-
- 26 Feb, 2008 11 commits
-
-
kent@mysql.com/kent-amd64.(none) authored
Use MYSQL_NUMERIC_VERSION, to make sure NDB_VERSION_BUILD is numeric
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/build/mysql-5.1-build
-
kent@mysql.com/kent-amd64.(none) authored
Use MYSQL_NUMERIC_VERSION, only three numbers separated with dot misc.m4, character_sets.m4, openssl.m4: Removed unneded semicolon
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/build/mysql-5.0-build
-
kent@mysql.com/kent-amd64.(none) authored
Corrected calculation of version id, incorrect last two digits if < 10 Keep "sp1" or "a" in MYSQL_NO_DASH_VERSION, to set correct version in RPM spec file Added MYSQL_NUMERIC_VERSION that is like MYSQL_NO_DASH_VERSION before Added clear doc how the different version variables differ SocketServer.cpp: Corrected typo in debug error message
-
anozdrin/alik@quad. authored
into quad.:/mnt/raid/alik/MySQL/devel/5.1-rt
-
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.0-rt-merged
-
davi@endora.local authored
into mysql.com:/Users/davi/mysql/mysql-5.1-runtime
-
kostja@dipika.(none) authored
-
davi@mysql.com/endora.local authored
Bug#34678 @@debug variable's incremental mode The problem is that the per-thread debugging settings stack wasn't being deallocated before the thread termination, leaking the stack memory. The chosen solution is to push a new state if the current is set to the initial settings and pop it (free) once the thread finishes.
-