- 22 Dec, 2004 3 commits
-
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
use configured hostnames for SHM transporter setup
-
- 21 Dec, 2004 18 commits
-
-
heikki@hundin.mysql.fi authored
into hundin.mysql.fi:/home/heikki/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
ifdef on version prior to 5.0
-
heikki@hundin.mysql.fi authored
Put back accidentally removed undef and remove a debug def
-
heikki@hundin.mysql.fi authored
Fix InnoDB bug: on HP-UX, with a 32-bit binary, InnoDB was only able to read or write <= 2 GB files; the reason was that InnoDB treated the return value of lseek() as a 32-bit integer; lseek was used on HP-UX-11 as a replacement for pread() and pwrite() because HAVE_BROKEN_PREAD was defined on that platform
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
NdbApi.hpp to include ndb_inti.h and ndb_cluster_connecion.hpp
-
bar@mysql.com authored
-
acurtis@pcgem.rdg.cyberkinetica.com authored
Check that the requested storage engine is enabled.
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
added missing copyright text moved ndb_init things to separate header file removed ndb_global include documented cluster connection class moved internal constants to NdbImpl.hpp class changed wait_until_ready behaviour somewhat
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-4.1.clean
-
hf@deer.(none) authored
-
ram@gw.mysql.r18.ru authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b7281
-
ram@gw.mysql.r18.ru authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b7281
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-4.1.clean
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-4.1.clean
-
hf@deer.(none) authored
-
sergefp@mysql.com authored
into mysql.com:/dbdata/psergey/mysql-4.1-order-bug
-
- 20 Dec, 2004 5 commits
-
-
sergefp@mysql.com authored
into mysql.com:/dbdata/psergey/mysql-4.1-bug6825
-
mwagner@here.mwagner.org authored
Increment from 4.0.23 to 4.0.24
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
moved NdbWaiter, m_ndb_cluster_connection, to impl class moved node selection things to cluster connection moved all private things to impl class added opts for shared memory and node selection changed opts handling somewhat; introduced enum for options and common handling of option variables added checks for transporter support automatic addition of shared mem transporters moved wait_until_ready code to cluster connection added control of usage of new node selection method
-
ram@gw.mysql.r18.ru authored
-
- 19 Dec, 2004 1 commit
-
-
konstantin@mysql.com authored
library: stmt_update_metadata (used when we update max_length in mysql_stmt_store_result) needs valid row->length.
-
- 18 Dec, 2004 12 commits
-
-
paul@frost.snake.net authored
Fix up mysql help messages.
-
paul@frost.snake.net authored
Convert @samp{c} to 'c', not c.
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.1-clean
-
-
-
georg@beethoven.local authored
-
into ltantony.rdg.cyberkinetica.homeunix.net:/usr/home/antony/work/bug7391.4
-
-
monty@mysql.com authored
-
matt@booty.(none) authored
I fixed the typos in the transaction-isolation comments. I fixed the spelling mistakes in the comment. It had tripped up a support customer as they couldn't start the server with transaction-isolation= read-commited
-
-
Add in missing privilege checks. Tests for the privileges.
-
- 17 Dec, 2004 1 commit
-
-
guilhem@mysql.com authored
Fix for BUG#7358: removing warning reporting of mysqldump 4.1.8 when calling SHOW CREATE DATABASE, as we deal almost gracefully with it (back to behaviour of 4.1.7). Warning was not fatal: mysqldump continued. And the good thing is that it helped spot that starting from 4.1.7, SHOW CREATE DATABASE failed (if --single-transaction and first db has non-empty InnoDB table and there is a second db) and thus mysqldump produced CREATE DATABASE statements missing the CHARACTER SET clause. Removing the bug which was in the server, and the warning reporting in mysqldump (compatibility with old servers).
-