- 16 Jun, 2005 2 commits
-
-
serg@serg.mylan authored
-
serg@serg.mylan authored
-
- 15 Jun, 2005 1 commit
-
-
serg@serg.mylan authored
portability alignment issues.
-
- 14 Jun, 2005 1 commit
-
-
pekka@mysql.com authored
into mysql.com:/export/space/pekka/ndb/version/my41
-
- 13 Jun, 2005 12 commits
-
-
tulin@dl145c.mysql.com authored
into dl145c.mysql.com:/home/ndbdev/tomas/mysql-4.1
-
tulin@dl145c.mysql.com authored
into dl145c.mysql.com:/home/ndbdev/tomas/mysql-4.1
-
igor@igor-inspiron.creware.com authored
Correction for test case of bug #11142.
-
igor@igor-inspiron.creware.com authored
Added a test case for bug #11142. item_cmpfunc.cc: Fixed bug #11142. Implementation of Item_func_nullif::is_null was corrected.
-
tulin@dl145c.mysql.com authored
Logging to logging@openlogging.org accepted DbtcMain.cpp, testTimeout.cpp: Bug #11290 TransactionInactiveTimeout = 0 does not result in infinite timeout
-
igor@igor-inspiron.creware.com authored
into igor-inspiron.creware.com:/home/igor/dev/mysql-4.1-0
-
pekka@mysql.com authored
-
igor@igor-inspiron.creware.com authored
Added a test case for bug #11167. sql_select.cc: Fixed bug #11167. In 4.1 char/varchar fields are limited by 255 characters in length that make them longer than 255 bytes in size for such character sets as UTF8. The functions store_record_in_cache and read_cached_records did not take into account this Moreover the code did not take into account that the size of the varchar fields in 5.0 can be up to 65535 bytes
-
lars@mysql.com authored
into mysql.com:/home/bk/b6883-mysql-4.1
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-4.1-push
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-4.1-push
-
joreland@mysql.com authored
Enable retry on startTransaction
-
- 10 Jun, 2005 11 commits
-
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
reggie@mdk10.(none) authored
into mdk10.(none):/home/reggie/bk/41test3
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.1-build
-
lenz@mysql.com authored
the SSL tests pass
-
joreland@mysql.com authored
Fix mem leak in testBlobs
-
joreland@mysql.com authored
Fix stack overflow in ndb_cpcd on amd64
-
joreland@mysql.com authored
script fixes for solaris
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-4.1-clean
-
- 09 Jun, 2005 13 commits
-
-
jimw@mysql.com authored
before a newline is found. (Bug #10840)
-
svoj@mysql.com authored
into mysql.com:/var/tmp/sslbug/mysql-4.1
-
acurtis@xiphis.org authored
into xiphis.org:/usr/home/antony/work2/p1-bug11028.3
-
acurtis@xiphis.org authored
Report error instead of crashing
-
reggie@mdk10.(none) authored
Without this patch, all file elements in info have symlink resolved pathnames. This means append_create_info does not have any way of showing the correct database name when a symlinked database is used.
-
konstantin@mysql.com authored
-
gluh@mysql.com authored
into mysql.com:/home/gluh/MySQL/Merge/4.1
-
joreland@mysql.com authored
-
gluh@eagle.intranet.mysql.r18.ru authored
generate proper error message if we use SET ... = NULL for 'set' variables
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-4.1-push
-
ramil@mysql.com authored
a fix (bug #11193: error messages gets garbled after reggies latest changeset: ChangeSet@1.2260.1.).
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-4.1-push
-
joreland@mysql.com authored
small script fixes - Don't use hostname -s as it's linux specific - Don't remove result unless scp worked
-