kent@mysql.com/kent-amd64.(none)
0886cc3bed
Many files:
...
Put back old code to check stack direction at configure time
2007-07-23 23:54:55 +02:00
gkodinov/kgeorge@magare.gmz
07acfcf557
coding style fix : Index_hint
2007-07-23 19:09:48 +03:00
gkodinov/kgeorge@magare.gmz
33518801fb
Merge gkodinov@bk-internal.mysql.com:/home/bk/mysql-5.0-opt
...
into magare.gmz:/home/kgeorge/mysql/autopush/B29644-5.0-opt
2007-07-23 17:07:29 +03:00
thek@adventure.(none)
7d55b07fca
Bug#28012 Patch : IM crashes instead of reporting an error when mysqldpath is bad
...
On the windows platform, if an instance object failed to initialize during
program start, the instance manager would crash.
This could happen if an incorrect mysqld path was supplied in the
defaults configuration file.
The patch prevents the program from crashing and makes it show an
error message instead.
2007-07-23 15:05:50 +02:00
igor@olga.mysql.com
5ae1392cb0
Merge ibabaev@bk-internal.mysql.com:/home/bk/mysql-5.0-opt
...
into olga.mysql.com:/home/igor/mysql-5.0-opt
2007-07-22 23:07:59 -07:00
gkodinov/kgeorge@magare.gmz
bc1a6ba954
table.cc, sql_select.cc:
...
Limit the fix for bug 28591 to InnoDB only
2007-07-23 06:26:57 +03:00
igor@olga.mysql.com
54f3949a27
Fixed bug #29611 .
...
If a primary key is defined over column c of enum type then
the EXPLAIN command for a look-up query of the form
SELECT * FROM t WHERE c=0
said that the query was with an impossible where condition though the
query correctly returned non-empty result set when the table indeed
contained rows with error empty strings for column c.
This kind of misbehavior was due to a bug in the function
Field_enum::store(longlong,bool) that erroneously returned 1 if
the the value to be stored was equal to 0.
Note that the method
Field_enum::store(const char *from,uint length,CHARSET_INFO *cs)
correctly returned 0 if a value of the error empty string
was stored.
2007-07-22 18:26:16 -07:00
baker@bk-internal.mysql.com
9cac726a8e
Merge bk-internal.mysql.com:/data0/bk/mysql-5.1
...
into bk-internal.mysql.com:/data0/bk/mysql-5.1-arch
2007-07-23 00:45:27 +02:00
istruewing@chilla.local
ab22b0a337
Merge chilla.local:/home/mydev/mysql-5.0-axmrg
...
into chilla.local:/home/mydev/mysql-5.1-axmrg
2007-07-22 21:07:22 +02:00
istruewing@chilla.local
b5cbd16378
Merge chilla.local:/home/mydev/mysql-5.1-amain
...
into chilla.local:/home/mydev/mysql-5.1-axmrg
2007-07-22 21:04:53 +02:00
istruewing@chilla.local
7c7ccc2f52
Merge chilla.local:/home/mydev/mysql-5.0-amain
...
into chilla.local:/home/mydev/mysql-5.0-axmrg
2007-07-22 19:08:25 +02:00
gkodinov/kgeorge@magare.gmz
7402fd6e79
Merge gkodinov@bk-internal.mysql.com:/home/bk/mysql-5.0-opt
...
into magare.gmz:/home/kgeorge/mysql/autopush/B28951-5.0-opt
2007-07-22 19:23:29 +03:00
holyfoot/hf@mysql.com/hfmain.(none)
57a564673b
Merge bk@192.168.21.1:mysql-4.1-opt
...
into mysql.com:/home/hf/work/29494/my41-29494
2007-07-22 18:16:11 +05:00
holyfoot/hf@hfmain.(none)
336d4848ab
Merge bk@192.168.21.1:mysql-5.0-opt
...
into mysql.com:/home/hf/work/29494/my50-29494
2007-07-22 18:13:39 +05:00
holyfoot/hf@hfmain.(none)
6a5b7b6a15
Merge bk@192.168.21.1:mysql-5.1-opt
...
into mysql.com:/home/hf/work/29494/my51-29494
2007-07-22 18:02:11 +05:00
holyfoot/hf@hfmain.(none)
56e6ae811f
Merge mysql.com:/home/hf/work/29494/my50-29494
...
into mysql.com:/home/hf/work/29494/my51-29494
2007-07-22 14:03:53 +05:00
holyfoot/hf@hfmain.(none)
14cbdecf7c
Merge mysql.com:/home/hf/work/29494/my41-29494
...
into mysql.com:/home/hf/work/29494/my50-29494
2007-07-22 14:03:18 +05:00
igor@olga.mysql.com
ce9ee1b9f3
Merge ibabaev@bk-internal.mysql.com:/home/bk/mysql-5.0-opt
...
into olga.mysql.com:/home/igor/mysql-5.0-opt
2007-07-21 15:46:02 -07:00
gshchepa/uchum@gleb.loc
58f0814c3b
Merge gleb.loc:/home/uchum/work/bk/5.0-opt
...
into gleb.loc:/home/uchum/work/bk/5.1-opt
2007-07-22 01:58:37 +05:00
gshchepa/uchum@gleb.loc
882bb64fc6
Merge gleb.loc:/home/uchum/work/bk/5.0-opt-29338
...
into gleb.loc:/home/uchum/work/bk/5.0-opt
2007-07-22 01:52:13 +05:00
gshchepa/uchum@gleb.loc
872d21eb1f
sp.test, sp.result:
...
Additional test case fix for bug #29338 .
2007-07-22 01:49:41 +05:00
igor@olga.mysql.com
233d5523ae
Merge olga.mysql.com:/home/igor/mysql-5.0-opt
...
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug29911
2007-07-21 13:36:33 -07:00
gshchepa/uchum@gleb.loc
f7010479fb
Merge gleb.loc:/home/uchum/work/bk/5.0-opt
...
into gleb.loc:/home/uchum/work/bk/5.1-opt
2007-07-22 00:53:01 +05:00
gshchepa/uchum@gleb.loc
2313bbc304
Merge gleb.loc:/home/uchum/work/bk/5.0-opt-29338
...
into gleb.loc:/home/uchum/work/bk/5.0-opt
2007-07-22 00:40:14 +05:00
igor@olga.mysql.com
43dab6b5de
Merge olga.mysql.com:/home/igor/dev-opt/mysql-4.1-opt-bug29911
...
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug29911
2007-07-21 12:34:18 -07:00
kostja@bodhi.(none)
cbd6e56ffa
Merge bodhi.(none):/opt/local/work/mysql-5.0-runtime
...
into bodhi.(none):/opt/local/work/mysql-5.1-runtime
2007-07-21 17:57:32 +04:00
kostja@bodhi.(none)
0e728d1463
Merge bk-internal.mysql.com:/home/bk/mysql-5.1
...
into bodhi.(none):/opt/local/work/mysql-5.1-runtime
2007-07-21 17:54:23 +04:00
kostja@bodhi.(none)
2ecd75ef24
Merge bk-internal.mysql.com:/home/bk/mysql-5.0
...
into bodhi.(none):/opt/local/work/mysql-5.0-runtime
2007-07-21 17:52:16 +04:00
joerg@trift2.
8b5f22a0c3
Merge trift2.:/MySQL/M50/push-5.0
...
into trift2.:/MySQL/M51/push-5.1
2007-07-21 12:36:37 +02:00
igor@olga.mysql.com
07e0cd2f4e
Fixed bug #29911 .
...
This bug manifested itself for join queries with GROUP BY and HAVING clauses
whose SELECT lists contained DISTINCT. It occurred when the optimizer could
deduce that the result set would have not more than one row.
The bug could lead to wrong result sets for queries of this type because
HAVING conditions were erroneously ignored in some cases in the function
remove_duplicates.
2007-07-20 22:56:19 -07:00
istruewing@chilla.local
1f00cbd774
Merge chilla.local:/home/mydev/mysql-5.0-axmrg
...
into chilla.local:/home/mydev/mysql-5.1-axmrg
2007-07-21 03:15:05 +02:00
istruewing@chilla.local
3a33c745f1
Merge bk-internal.mysql.com:/home/bk/mysql-5.1
...
into chilla.local:/home/mydev/mysql-5.1-axmrg
2007-07-21 03:13:59 +02:00
istruewing@chilla.local
410e4400c4
Merge chilla.local:/home/mydev/mysql-5.1-amain
...
into chilla.local:/home/mydev/mysql-5.1-axmrg
2007-07-21 03:12:35 +02:00
istruewing@chilla.local
d9bd5f2364
Merge chilla.local:/home/mydev/mysql-5.1-ateam
...
into chilla.local:/home/mydev/mysql-5.1-axmrg
2007-07-21 03:10:23 +02:00
gshchepa/uchum@gleb.loc
a5075a68be
Merge gleb.loc:/home/uchum/work/bk/5.0-opt
...
into gleb.loc:/home/uchum/work/bk/5.1-opt
2007-07-21 05:32:01 +05:00
gshchepa/uchum@gleb.loc
4990843b83
Merge gleb.loc:/home/uchum/work/bk/5.0-opt-29788
...
into gleb.loc:/home/uchum/work/bk/5.0-opt
2007-07-21 05:15:16 +05:00
kent@kent-amd64.(none)
9d247f296a
Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-5.0
...
into mysql.com:/home/kent/bk/tmp3/mysql-5.0-build
2007-07-21 01:53:19 +02:00
kent@kent-amd64.(none)
60b78f9f1a
Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-5.1
...
into mysql.com:/home/kent/bk/tmp3/mysql-5.1-build
2007-07-21 01:52:15 +02:00
gshchepa/uchum@gleb.loc
c3e925eec3
Fixed bug #29788 .
...
After dumping triggers mysqldump copied
the value of the OLD_SQL_MODE variable to the SQL_MODE
variable. If the --compact option of the mysqldump was
not set the OLD_SQL_MODE variable had the value
of the uninitialized SQL_MODE variable. So
usually the NO_AUTO_VALUE_ON_ZERO option of the
SQL_MODE variable was discarded.
This fix is for non-"--compact" mode of the mysqldump,
because mysqldump --compact never set SQL_MODE to the
value of NO_AUTO_VALUE_ON_ZERO.
The dump_triggers_for_table function has been modified
to restore previous value of the SQL_MODE variable after
dumping triggers using the SAVE_SQL_MODE temporary
variable.
2007-07-21 04:50:11 +05:00
istruewing@chilla.local
0a5d8f43b7
Merge chilla.local:/home/mydev/mysql-5.0-amain
...
into chilla.local:/home/mydev/mysql-5.0-axmrg
2007-07-21 01:34:55 +02:00
istruewing@chilla.local
4f60ac5242
Merge chilla.local:/home/mydev/mysql-5.0-ateam
...
into chilla.local:/home/mydev/mysql-5.0-axmrg
2007-07-21 01:33:25 +02:00
gshchepa/uchum@gleb.loc
27f11688da
Merge gleb.loc:/home/uchum/work/bk/5.0-opt
...
into gleb.loc:/home/uchum/work/bk/5.1-opt
2007-07-21 02:25:39 +05:00
acurtis/antony@xiphis.org/ltamd64.xiphis.org
c1ca591f09
silence two 'unused variable' warnings
2007-07-20 14:01:37 -07:00
acurtis/antony@ltamd64.xiphis.org
3d7ce2ce9c
Merge xiphis.org:/anubis/antony/work/mysql-5.1-engines
...
into xiphis.org:/anubis/antony/work/p1-bug29875.1
2007-07-20 12:35:15 -07:00
acurtis/antony@xiphis.org/ltamd64.xiphis.org
395233b4f7
Bug#29875
...
"Disable transaction support in Federated storage engine"
Minimal patch to disable Federated's transactions until they can be fixed.
2007-07-20 11:35:19 -07:00
gkodinov/kgeorge@magare.gmz
8fc401e21f
Bug #28591 : MySQL need not sort the records in case of
...
ORDER BY primary_key on InnoDB table
Queries that use an InnoDB secondary index to retrieve
data don't need to sort in case of ORDER BY primary key
if the secondary index is compared to constant(s).
They can also skip sorting if ORDER BY contains both the
the secondary key parts and the primary key parts (in
that order).
This is because InnoDB returns the rows in order of the
primary key for rows with the same values of the secondary
key columns.
Fixed by preventing temp table sort for the qualifying
queries.
2007-07-20 21:05:29 +03:00
evgen@moonbone.local
e50e8c94fc
Merge epotemkin@bk-internal.mysql.com:/home/bk/mysql-5.0-opt
...
into moonbone.local:/mnt/gentoo64/work/29898-bug-5.0-opt-mysql
2007-07-20 22:05:20 +04:00
kostja@bodhi.(none)
a6abf20f2e
Fix the coding style.
2007-07-20 19:52:25 +04:00
kostja@bodhi.(none)
6352d006a4
Merge bodhi.(none):/opt/local/work/mysql-5.0-runtime
...
into bodhi.(none):/opt/local/work/mysql-5.1-runtime
2007-07-20 19:50:55 +04:00
kostja@bodhi.(none)
19ae62f3fb
Remove obvious comments.
2007-07-20 19:46:13 +04:00