kroki/tomash@moonlight.intranet
e7ebeac561
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug23383
2006-11-17 12:40:42 +03:00
kroki/tomash@moonlight.intranet
6d4558f7c3
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug23383
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug23383
2006-11-17 12:30:26 +03:00
kroki/tomash@moonlight.intranet
5e2ef3a68e
BUG#23383: mysql_affected_rows() returns different values than
...
mysql_stmt_affected_rows()
The problem was that affected_rows for prepared statement wasn't updated
in the client library on the error. The solution is to always update
affected_rows, which will be equal to -1 on the error.
2006-11-17 12:21:32 +03:00
holyfoot/hf@mysql.com/deer.(none)
dac2d0fcba
merging
2006-11-17 12:02:36 +04:00
holyfoot/hf@mysql.com/deer.(none)
950665fc3b
merging
2006-11-17 11:15:40 +04:00
holyfoot/hf@mysql.com/deer.(none)
e95e23b0f3
Merge bk@192.168.21.1:mysql-5.0-opt
...
into mysql.com:/home/hf/work/mysql-5.0-0mrg
2006-11-17 10:30:16 +04:00
bell@desktop.sanja.is.com.ua
d56ab5afb6
Fix of debbuging mode of query cache (proposed by Monty reviewed by me).
2006-11-17 08:18:10 +02:00
pekka@orca.ndb.mysql.com
5e6b587239
Merge orca.ndb.mysql.com:/export/home/space/pekka/ndb/version/my50-ndb
...
into orca.ndb.mysql.com:/export/home/space/pekka/ndb/version/my50-misc
2006-11-16 21:13:10 +01:00
joerg@trift2.
7ede3508c8
Merge trift2.:/MySQL/M41/push-4.1
...
into trift2.:/MySQL/M50/push-5.0
2006-11-16 21:07:08 +01:00
joerg@trift2.
3a12df0bb9
Merge trift2.:/MySQL/M41/mysql-4.1
...
into trift2.:/MySQL/M41/push-4.1
2006-11-16 21:04:01 +01:00
joerg@trift2.
aa5b64f98b
Merge trift2.:/MySQL/M50/tmp-5.0
...
into trift2.:/MySQL/M50/push-5.0
2006-11-16 21:01:52 +01:00
holyfoot/hf@mysql.com/deer.(none)
497ccd6b87
Merge mysql.com:/home/hf/work/mysql-4.1-mrg
...
into mysql.com:/home/hf/work/mysql-5.0-mrg
2006-11-16 23:16:44 +04:00
holyfoot/hf@mysql.com/deer.(none)
e7cde72651
merging
2006-11-16 23:00:48 +04:00
holyfoot/hf@mysql.com/deer.(none)
2963d8ddd2
merging
2006-11-16 21:23:34 +04:00
holyfoot/hf@mysql.com/deer.(none)
db5db841a9
Merge bk@192.168.21.1:mysql-4.1
...
into mysql.com:/home/hf/work/mysql-4.1-mrg
2006-11-16 20:44:37 +04:00
joerg@trift2.
a2b1f2c187
Merge trift2.:/MySQL/M50/bug22081-5.0
...
into trift2.:/MySQL/M50/push-5.0
2006-11-16 14:47:05 +01:00
joerg@trift2.
818f3fa21f
Merge trift2.:/MySQL/M41/bug22081-4.1
...
into trift2.:/MySQL/M50/bug22081-5.0
2006-11-16 14:38:15 +01:00
joerg@trift2.
29dd8d2e58
support-files/mysql.spec.sh : Add an "Obsoletes" note relative to SuSE RPMs (bug#22081).
2006-11-16 14:01:31 +01:00
kroki/tomash@moonlight.intranet
2b9bcb2c3c
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug17047
2006-11-16 14:19:37 +03:00
kroki/tomash@moonlight.intranet
690cb27d05
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-runtime
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug17047
2006-11-16 14:15:56 +03:00
kroki/tomash@moonlight.intranet
9e7f682116
Add 5.0 part of fix for bug 17047.
2006-11-16 14:06:51 +03:00
kroki/tomash@moonlight.intranet
23efecdb3c
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug17047
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug17047
2006-11-16 13:25:55 +03:00
kroki/tomash@moonlight.intranet
b8d5451565
BUG#17047: CHAR() and IN() can return NULL without signaling NULL result
...
The problem was that some functions (namely IN() starting with 4.1, and
CHAR() starting with 5.0) were returning NULL in certain conditions,
while they didn't set their maybe_null flag. Because of that there could
be some problems with 'IS NULL' check, and statements that depend on the
function value domain, like CREATE TABLE t1 SELECT 1 IN (2, NULL);.
The fix is to set maybe_null correctly.
2006-11-16 13:21:38 +03:00
joerg@trift2.
66142e76c5
Merge trift2.:/MySQL/M50/spec-mtr-5.0
...
into trift2.:/MySQL/M50/clone-5.0
2006-11-15 20:39:04 +01:00
joerg@trift2.
28fe4a5501
Merge trift2.:/MySQL/M50/spec-mtr-5.0
...
into trift2.:/MySQL/M50/push-5.0
2006-11-15 20:36:33 +01:00
joerg@trift2.
844d5161fc
Merge trift2.:/MySQL/M41/spec-mtr-4.1
...
into trift2.:/MySQL/M50/spec-mtr-5.0
2006-11-15 20:34:44 +01:00
joerg@trift2.
65d6b24ed9
support-files/mysql.spec.sh : Use "report features" in the first test run.
2006-11-15 20:27:02 +01:00
lars@mysql.com/black.(none)
4e9ef283ef
Dummy push to force pushbuild retest
2006-11-15 19:17:52 +01:00
lars@mysql.com/black.(none)
8da4385e3d
Merge mysql.com:/home/bkroot/mysql-5.0
...
into mysql.com:/home/bk/MERGE/mysql-5.0-merge
2006-11-15 13:11:25 +01:00
lars@mysql.com/black.(none)
021d85f032
Merge mysql.com:/home/bk/MERGE/mysql-4.1-merge
...
into mysql.com:/home/bk/MERGE/mysql-5.0-merge
2006-11-15 12:41:51 +01:00
lars@mysql.com/black.(none)
ea3915dbe5
Merge mysql.com:/home/bkroot/mysql-5.0-rpl
...
into mysql.com:/home/bk/MERGE/mysql-5.0-merge
2006-11-15 12:40:07 +01:00
lars@mysql.com/black.(none)
a6801d4fe4
Merge mysql.com:/home/bkroot/mysql-4.1-rpl
...
into mysql.com:/home/bk/MERGE/mysql-4.1-merge
2006-11-15 12:39:21 +01:00
aelkin/elkin@dsl-hkibras-fe30f900-107.dhcp.inet.fi
10767f3f9a
Merge dsl-hkibras-fe30f900-107.dhcp.inet.fi:/home/elkin/MySQL/TEAM/BARE/4.1
...
into dsl-hkibras-fe30f900-107.dhcp.inet.fi:/home/elkin/MySQL/TEAM/BARE/5.0
2006-11-15 12:55:43 +02:00
aelkin/elkin@dsl-hkibras-fe30f900-107.dhcp.inet.fi
5235785b2e
bug#19402 SQL close to the size of the max_allowed_packet fails on the slave
...
mending windows test.
2006-11-15 12:53:07 +02:00
evgen@moonbone.local
5198354584
Bug#20045: Server crash on INSERT ... SELECT ... FROM non-mergeable view
...
The regression is caused by the fix for bug 14767. When INSERT ... SELECT
used a view in the SELECT list that was not inlined, and there was an
active transaction, the server could crash in Query_cache::invalidate.
On INSERT ... SELECT only the table being inserted into is invalidated.
Thus views that can't be inlined are skipped from invalidation.
The bug manifests itself in two ways so there is 2 test cases.
One checks that the only the table being inserted into is invalidated.
And the second one checks that there is no crash on INSERT ... SELECT.
2006-11-14 19:50:44 +03:00
df@kahlann.erinye.com
fc4530f1bd
Merge dfischer@bk-internal.mysql.com:/home/bk/mysql-5.0
...
into kahlann.erinye.com:/home/df/mysql/build/mtr-5.0
2006-11-14 15:27:55 +01:00
df@kahlann.erinye.com
68335d812d
Merge dev:my/mysql-5.0-release
...
into kahlann.erinye.com:/home/df/mysql/build/mtr-5.0
2006-11-14 14:58:59 +01:00
df@kahlann.erinye.com
4dd2d7062a
Merge kahlann.erinye.com:/home/df/mysql/build/mtr-4.1
...
into kahlann.erinye.com:/home/df/mysql/build/mtr-5.0
2006-11-14 14:48:29 +01:00
df@kahlann.erinye.com
5d8525c6f7
make_binary_distribution should of course also copy .test files from mysql-test/include
2006-11-14 14:44:20 +01:00
df@kahlann.erinye.com
cc129e6256
Merge kahlann.erinye.com:/home/df/mysql/build/mtr-4.1
...
into kahlann.erinye.com:/home/df/mysql/build/mtr-5.0
2006-11-14 14:29:58 +01:00
df@kahlann.erinye.com
a863fbbf41
make dist now copies .test files in mysql-test/include
2006-11-14 14:29:05 +01:00
joerg/mysqldev@mysql.com/production.mysql.com
2ddb61eb93
Raise version number after cloning 5.0.30
2006-11-14 13:37:10 +01:00
joerg@trift2.
d22948a193
Merge trift2.:/MySQL/M50/clone-5.0
...
into trift2.:/MySQL/M50/mysql-5.0
2006-11-14 12:47:53 +01:00
aelkin/elkin@dsl-hkibras-fe30f900-107.dhcp.inet.fi
650a245568
bug#19402 SQL close to the size of the max_allowed_packet fails on the slave
...
ver 5.0 and 5.1 refinement.
adding to the MAX_SIZE_LOG_EVENT_STATUS estimation status vars and
EXECUTE_LOAD_QUERY_EXTRA_HEADER_LEN
2006-11-14 12:48:17 +02:00
mskold/marty@mysql.com/linux.site
a40f5dfbac
Merge mskold@bk-internal.mysql.com:/home/bk/mysql-5.0-ndb
...
into mysql.com:/windows/Linux_space/MySQL/mysql-5.0-ndb
2006-11-14 11:38:57 +01:00
mskold/marty@mysql.com/linux.site
7c3cb3d86d
Merge mskold@bk-internal.mysql.com:/home/bk/mysql-5.0
...
into mysql.com:/windows/Linux_space/MySQL/mysql-5.0-ndb
2006-11-14 10:06:11 +01:00
malff/marcsql@weblab.(none)
429b0e6c0f
Bug#23703 (DROP TRIGGER needs an IF EXISTS)
...
This change set implements the DROP TRIGGER IF EXISTS functionality.
This fix is considered a bug and not a feature, because without it,
there is no known method to write a database creation script that can create
a trigger without failing, when executed on a database that may or may not
contain already a trigger of the same name.
Implementing this functionality closes an orthogonality gap between triggers
and stored procedures / stored functions (which do support the DROP IF
EXISTS syntax).
In sql_trigger.cc, in mysql_create_or_drop_trigger,
the code has been reordered to:
- perform the tests that do not depend on the file system (access()),
- get the locks (wait_if_global_read_lock, LOCK_open)
- call access()
- perform the operation
- write to the binlog
- unlock (LOCK_open, start_waiting_global_read_lock)
This is to ensure that all the code that depends on the presence of the
trigger file is executed in the same critical section,
and prevents race conditions similar to the case fixed by Bug 14262 :
- thread 1 executes DROP TRIGGER IF EXISTS, access() returns a failure
- thread 2 executes CREATE TRIGGER
- thread 2 logs CREATE TRIGGER
- thread 1 logs DROP TRIGGER IF EXISTS
The patch itself is based on code contributed by the MySQL community,
under the terms of the Contributor License Agreement (See Bug 18161).
2006-11-13 15:40:22 -07:00
lars@mysql.com/black.(none)
7aa562ad20
Merge mysql.com:/home/bk/MERGE/mysql-4.1-merge
...
into mysql.com:/home/bk/MERGE/mysql-5.0-merge
2006-11-13 17:54:01 +01:00
hartmut@mysql.com/linux.site
639683919d
Fix for Bug #23887 (Introduced by Bugfix #22295 )
2006-11-13 17:04:40 +01:00
gkodinov/kgeorge@rakia.gmz
e347eb1995
Merge gkodinov@bk-internal.mysql.com:/home/bk/mysql-4.1-opt
...
into rakia.gmz:/home/kgeorge/mysql/autopush/B19216-4.1-opt
2006-11-13 15:40:19 +02:00