kroki/tomash@moonlight.intranet
b7fd43bcd0
Merge bk-internal.mysql.com:/home/bk/mysql-5.0-runtime
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-cleanup
2006-11-03 12:47:31 +03:00
kroki/tomash@moonlight.intranet
1dbf98d162
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-cleanup
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-cleanup
2006-11-03 12:25:34 +03:00
kroki/tomash@moonlight.intranet
fbf508d686
Cleanup: fix race in rename.test.
2006-11-03 12:16:31 +03:00
anozdrin/alik@booka.
7096cd20a4
Wait for IM to start accepting connections after restart (part 2).
2006-11-02 21:43:52 +03:00
anozdrin/alik@booka.
8bc5a89178
Wait for IM to start accepting connections after restart.
2006-11-02 16:53:14 +03:00
kostja@bodhi.local
5196eadc06
Merge bodhi.local:/opt/local/work/mysql-4.1-runtime
...
into bodhi.local:/opt/local/work/mysql-5.0-runtime-merge
2006-11-02 02:38:41 +03:00
kostja@bodhi.local
b471ea50f7
Merge bk-internal.mysql.com:/home/bk/mysql-5.0
...
into bodhi.local:/opt/local/work/mysql-5.0-runtime-merge
2006-11-02 01:21:37 +03:00
kostja@bodhi.local
6a28c436f7
Merge bk-internal.mysql.com:/home/bk/mysql-4.1
...
into bodhi.local:/opt/local/work/mysql-4.1-runtime
2006-11-02 01:08:39 +03:00
jonas@perch.ndb.mysql.com
7acfde913a
ndb - revert bug to wait for "proper" bug fix
...
bug#21052
2006-11-01 16:14:49 +01:00
dlenev@mockturtle.local
5961d4721f
Merge bk-internal.mysql.com:/home/bk/mysql-5.0-runtime
...
into mockturtle.local:/home/dlenev/src/mysql-5.0-hash-2
2006-11-01 16:20:15 +03:00
dlenev@mockturtle.local
bd1b57f930
Small cleanup in code handling stored routines/table prelocking.
...
Use lazy initialization for Query_tables_list::sroutines hash.
This step should significantly decrease amount of memory consumed
by stored routines as we no longer will allocate chunk of memory
required for this HASH for each statement in routine.
2006-11-01 15:41:48 +03:00
jonas@perch.ndb.mysql.com
543e73d663
Merge perch.ndb.mysql.com:/home/jonas/src/50-multi
...
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-ndb
2006-10-31 16:15:15 +01:00
jonas@perch.ndb.mysql.com
c6308d652d
ndb - ndb_multi spurious failure
...
remove timeing dependant part of test
2006-10-31 16:09:31 +01:00
kroki/tomash@moonlight.intranet
75881599e5
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug21915
2006-10-30 17:59:23 +03:00
kroki/tomash@moonlight.intranet
77f1d01fbb
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-runtime
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug21915
2006-10-30 17:58:56 +03:00
kroki/tomash@moonlight.intranet
1c87434699
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug21915
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug21915
2006-10-30 17:51:36 +03:00
kroki/tomash@moonlight.intranet
1bfe00e0da
BUG#21915: Changing limits of table_cache when setting max_connections
...
If the user has specified --max-connections=N or --table-open-cache=M
options to the server, a warning could be given that some values were
recalculated, and table-open-cache could be assigned greater value.
Note that both warning and increase of table-open-cache were totally
harmless.
This patch fixes recalculation code to ensure that table-open-cache will
be never increased automatically and that a warning will be given only if
some values had to be decreased due to operating system limits.
No test case is provided because we neither can't predict nor control
operating system limits for maximal number of open files.
2006-10-30 17:47:02 +03:00
kostja@bodhi.local
dfc4dd423c
A cleanup.
2006-10-30 12:03:42 +03:00
kostja@bodhi.local
8143148bc1
Cleanup.
2006-10-30 11:36:30 +03:00
kostja@bodhi.local
b94f939c5a
Merge bk-internal.mysql.com:/home/bk/mysql-5.0
...
into bodhi.local:/opt/local/work/mysql-5.0-runtime
2006-10-30 10:05:43 +03:00
jonas@perch.ndb.mysql.com
b67e5b1131
Merge perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
...
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-ndb
2006-10-27 23:59:04 +02:00
jonas@perch.ndb.mysql.com
dc2ca8ca10
Merge perch.ndb.mysql.com:/home/jonas/src/mysql-4.1
...
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
2006-10-27 23:56:51 +02:00
jonas@perch.ndb.mysql.com
f4af143fcb
Merge joreland@bk-internal.mysql.com:/home/bk/mysql-4.1-ndb
...
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
2006-10-27 23:54:57 +02:00
jonas@perch.ndb.mysql.com
85b0e1f80b
Merge perch.ndb.mysql.com:/home/jonas/src/41-work
...
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
2006-10-27 23:54:24 +02:00
jonas@perch.ndb.mysql.com
3b726b2845
Merge perch.ndb.mysql.com:/home/jonas/src/50-work
...
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-ndb
2006-10-27 16:41:06 +02:00
jonas@perch.ndb.mysql.com
4037a8d657
Merge perch.ndb.mysql.com:/home/jonas/src/41-work
...
into perch.ndb.mysql.com:/home/jonas/src/50-work
2006-10-27 16:34:22 +02:00
jonas@perch.ndb.mysql.com
0cbb309b1a
ndb - valgrind
...
Still leakage, make sure all unlinked operations are put back so they will be release
(on failing blob operations, when AO_IgnoreError)
2006-10-27 16:32:59 +02:00
kroki/tomash@moonlight.intranet
43e84da003
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug22584
2006-10-27 13:47:45 +04:00
kroki/tomash@moonlight.intranet
0e0f7a0423
BUG#22584: last_insert_id not updated after inserting a record through
...
a updatable view.
When there's a VIEW on a base table that have AUTO_INCREMENT column, and
this VIEW doesn't provide an access such column, after INSERT to such
VIEW LAST_INSERT_ID() did not return the value just generated.
This behaviour is intended and correct, because if the VIEW doesn't list
some columns then these columns are effectively hidden from the user,
and so any side effects of inserting default values to them.
However, there was a bug that such statement inserting into a view would
reset LAST_INSERT_ID() instead of leaving it unchanged.
This patch restores the original value of LAST_INSERT_ID() instead of
resetting it to zero.
2006-10-27 13:32:41 +04:00
pekka@orca.ndb.mysql.com
7236064342
Merge pnousiainen@bk-internal.mysql.com:/home/bk/mysql-5.0-ndb
...
into orca.ndb.mysql.com:/export/home/space/pekka/ndb/version/my50-ndb
2006-10-25 21:03:01 +02:00
kroki/tomash@moonlight.intranet
99baff565e
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug18819
2006-10-25 20:16:39 +04:00
kroki/tomash@moonlight.intranet
fa60a03073
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-runtime
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug18819
2006-10-25 20:13:07 +04:00
kroki/tomash@moonlight.intranet
2c03444971
Fix after manual merge.
2006-10-25 20:09:31 +04:00
kroki/tomash@moonlight.intranet
c8bb2f396a
Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug18819
...
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug18819
2006-10-25 20:00:51 +04:00
kroki/tomash@moonlight.intranet
b7b991cec3
BUG#18819: DELETE IGNORE hangs on foreign key parent delete
...
If the error happens during DELETE IGNORE, nothing could be send to the
client, thus leaving it frozen expecting the reply.
The problem was that if some error occurred, it wouldn't be reported to
the client because of IGNORE, but neither success would be reported.
MySQL 4.1 would not freeze the client, but will report
ERROR 1105 (HY000): Unknown error
instead, which is also a bug.
The solution is to report success if we are in DELETE IGNORE and some
non-fatal error has happened.
2006-10-25 19:53:26 +04:00
pekka@orca.ndb.mysql.com
00db3c9982
ndb - dbtux: remove redundant code line (no functional change)
2006-10-25 17:30:30 +02:00
mskold/marty@mysql.com/linux.site
7ad30e80f1
Merge mskold@bk-internal.mysql.com:/home/bk/mysql-4.1-ndb
...
into mysql.com:/windows/Linux_space/MySQL/mysql-4.1-ndb
2006-10-25 15:17:44 +02:00
mskold/marty@mysql.com/linux.site
c14c547289
Merge mysql.com:/windows/Linux_space/MySQL/mysql-5.0
...
into mysql.com:/windows/Linux_space/MySQL/mysql-5.0-ndb
2006-10-25 12:41:42 +02:00
mskold/marty@mysql.com/linux.site
0dea24947d
Merge mysql.com:/windows/Linux_space/MySQL/mysql-4.1
...
into mysql.com:/windows/Linux_space/MySQL/mysql-5.0
2006-10-25 12:21:45 +02:00
mskold/marty@mysql.com/linux.site
deb26a93e5
Merge mysql.com:/windows/Linux_space/MySQL/mysql-4.1
...
into mysql.com:/windows/Linux_space/MySQL/mysql-4.1-ndb
2006-10-25 11:45:47 +02:00
mskold/marty@mysql.com/linux.site
44e55e3b43
Bug #21072 Duplicate key error in NDB references wrong key: Re-wrote string usage to avoid valgrind warnings
2006-10-25 11:44:40 +02:00
knielsen@ymer.(none)
df8c9272e8
Merge ymer.(none):/usr/local/mysql/mysql-4.1-ndb.tmp
...
into ymer.(none):/usr/local/mysql/mysql-4.1-ndb
2006-10-25 10:46:00 +02:00
knielsen@ymer.(none)
6445ae3312
Merge ymer.(none):/usr/local/mysql/mysql-4.1-ndb.tmp
...
into ymer.(none):/usr/local/mysql/mysql-5.0-ndb
2006-10-25 10:45:11 +02:00
knielsen@ymer.(none)
44aa0f4de1
Fix two small problems in the source, potentially causing user-visible
...
bugs.
2006-10-25 10:37:53 +02:00
stewart@willster.(none)
a4faddc64f
Merge bk-internal.mysql.com:/home/bk/mysql-4.1-ndb
...
into willster.(none):/home/stewart/Documents/MySQL/4.1/bug19914-mk2-merge2
2006-10-25 17:24:20 +10:00
jonas@perch.ndb.mysql.com
0f74244d86
Merge perch.ndb.mysql.com:/home/jonas/src/41-work
...
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-ndb
2006-10-25 08:40:34 +02:00
jonas@perch.ndb.mysql.com
61f87f5d3c
Merge perch.ndb.mysql.com:/home/jonas/src/50-work
...
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-ndb
2006-10-25 08:31:30 +02:00
jonas@perch.ndb.mysql.com
6e4a0ec042
Merge joreland@bk-internal.mysql.com:/home/bk/mysql-5.0-ndb
...
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-ndb
2006-10-25 08:28:30 +02:00
pekka@orca.ndb.mysql.com
64c414a004
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-tux
2006-10-24 20:52:09 +02:00
stewart@willster.(none)
a8037f478d
fix result file for ndb_multi
2006-10-25 00:41:55 +10:00