- 09 Dec, 2004 1 commit
-
-
brian@avenger.(none) authored
A few simple fixes plus the added support of being able to repair the meta data file via REPAIR TABLE. More information is now provided in SHOW TABLE STATUS.
-
- 07 Dec, 2004 4 commits
-
-
jani@ua141d10.elisa.omakaista.fi authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com authored
Fixed compiler warnings String results in CREATE ... SELECT are now created as CHAR(0), VARCHAR(X) or TEXT() depending on item->max_length
-
brian@avenger.(none) authored
-
- 06 Dec, 2004 13 commits
-
-
brian@avenger.(none) authored
-
monty@mysql.com authored
-
brian@avenger.(none) authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com authored
Fixed compiler warnings Fix core dump when sending SIGHUP to mysqld
-
serg@serg.mylan authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-5.0
-
serg@serg.mylan authored
handle test_ro(".999", 0, HALF_UP, "1");
-
monty@mysql.com authored
-
brian@avenger.(none) authored
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-5.0
-
gluh@gluh.mysql.r18.ru authored
#6950 mysql-nt.exe error when click on sql or database on mysql control center
-
monty@mysql.com authored
Renamed HA_VAR_LENGTH to HA_VAR_LENGTH_PART Renamed in all files FIELD_TYPE_STRING and FIELD_TYPE_VAR_STRING to MYSQL_TYPE_STRING and MYSQL_TYPE_VAR_STRING to make it easy to catch all possible errors Added support for VARCHAR KEYS to heap Removed support for ISAM Now only long VARCHAR columns are changed to TEXT on demand (not CHAR) Internal temporary files can now use fixed length tables if the used VARCHAR columns are short
-
- 05 Dec, 2004 1 commit
-
-
monty@mysql.com authored
-
- 04 Dec, 2004 4 commits
-
-
brian@avenger.(none) authored
Would you believe that I wrote all of this on a Mac? I just happen to be not using HFS for the partition I did this work on. Oops :)
-
pekka@mysql.com authored
-
lars@mysql.com authored
-
brian@avenger.(none) authored
into avenger.(none):/export/brian/mysql/acinclude-5.0
-
- 03 Dec, 2004 17 commits
-
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-5.0
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-qc-4.1
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-global-4.1
-
jimw@mysql.com authored
-
jimw@mysql.com authored
-
marko@hundin.mysql.fi authored
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-5.0
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-4.1
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-4.1
-
lars@mysql.com authored
1 if the return type is int or int_fast8_t. The test case that showed this problem is rpl000001 and the tested version was MySQL 5.0.2. The compiler with the problem is GCC 3.0.4 runing on "Linux bitch 2.4.18 #2 Thu Apr 11 14:37:17 EDT 2002 sparc64 unknown". By changing the return type to bool the problem disappear. (Another way to make the problem disappear is to simply print the returned value with printf("%d",?). The printed returned value is always 0 in the test cases I have run.) This is only a partial solution to the problem, since someone could later change the return type of the function back to int or some other type that does not work.
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-4.1
-
serg@serg.mylan authored
Bug #6284 - report truncation warnings in INSERT ... SELECT only for "INSERT" part sql/sql_insert.cc Bug #6284 - report truncation warnings in INSERT ... SELECT only for "INSERT" part
-
joreland@mysql.com authored
-