monty@mysql.com
563500994a
Update results for new varchar handling
...
Fixed compiler warnings
String results in CREATE ... SELECT are now created as CHAR(0), VARCHAR(X) or TEXT() depending on item->max_length
2004-12-07 15:47:00 +02:00
monty@mysql.com
77207d19f2
Merge with new VARCHAR code
2004-12-06 19:18:35 +02:00
monty@mysql.com
0de4777187
Merge with 4.1
2004-12-06 11:38:56 +02:00
monty@mysql.com
67ce247965
Add support for up to VARCHAR (size up to 65535)
...
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
2004-12-06 02:00:37 +02:00
serg@serg.mylan
da92505db7
myisam/mi_packrec.c
...
more robust checks (catch more corruptions)
2004-12-02 15:14:36 +01:00
serg@serg.mylan
dd7ff9335a
one more test for corrupted compressed MyISAM table
2004-12-01 22:46:39 +01:00
tomas@poseidon.ndb.mysql.com
538a3f7a53
Merge tulin@bk-internal.mysql.com:/home/bk/mysql-4.1
...
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
2004-11-25 13:33:31 +00:00
serg@serg.mylan
e8203e437a
bug#6784
...
mi_flush_bulk_insert (on dup key error in mi_write)
was mangling info->dupp_key_pos
2004-11-24 23:16:16 +01:00
serg@serg.mylan
cd463b5202
harmless "buffer overflow" fixed
2004-11-24 11:01:54 +01:00
serg@serg.mylan
508067420e
Merge serg.mylan:/usr/home/serg/Abk/mysql-4.1
...
into serg.mylan:/usr/home/serg/Abk/mysql-5.0
2004-11-23 15:50:29 +01:00
serg@serg.mylan
48e7c9abc6
use FT_MAX_WORD_LEN_FOR_SORT instead of HA_FT_MAXBYTELEN when calculating
...
preferred key block length for ft index
2004-11-23 15:03:16 +01:00
serg@serg.mylan
ee933cd198
merged
2004-11-22 21:33:15 +01:00
serg@serg.mylan
2ca5a0f2b1
merged
2004-11-22 20:15:48 +01:00
serg@serg.mylan
b7aa981578
"Table file %s was created in MySQL 4.1+" is an error, not a warning
2004-11-22 19:18:35 +01:00
serg@serg.mylan
dca2182fdc
ft_boolean_search.c:
...
bug#6705 - (+trunc1* +trunc2*)
fulltext.test, fulltext.result:
bug#6705
2004-11-22 18:37:30 +01:00
serg@serg.mylan
e68bd85b77
merged
2004-11-17 18:04:36 +01:00
serg@serg.mylan
37e872de8c
merged
2004-11-17 15:28:37 +01:00
serg@serg.mylan
3d67df4cff
wrong constant fixed - boolean fulltext searches like "+something +smth*"
...
were stopping at docid 0xffffffff
2004-11-12 22:55:00 +01:00
monty@mysql.com
addd1a0da8
Merge with 4.1
2004-11-12 19:58:24 +02:00
monty@mysql.com
e9c3887b58
After merge fixes
2004-11-12 17:44:17 +02:00
brian@avenger.(none)
1d8a6a06a5
Merge avenger.(none):/export/brian/mysql/test/4.1
...
into avenger.(none):/export/brian/mysql/test/5.0
2004-11-11 22:12:01 -08:00
serg@serg.mylan
0be3c55594
mi_write: fix for ft2 when found word (in the tree) has different length as the word to insert
2004-11-11 21:26:24 +01:00
monty@mysql.com
071001950e
Merge with 4.1 to get in latest bug fixes
2004-11-04 15:06:24 +02:00
ram@gw.mysql.r18.ru
e1979f2580
A fix (bug #6309 : myisamchk compiled without debug support , --help shows vise versa
...
bug #6380 : mysqlcheck --help prints wrong --debug msg for non-debug version).
2004-11-02 13:14:07 +04:00
monty@mysql.com
afbe601302
merge with 4.1
2004-10-29 19:26:52 +03:00
serg@serg.mylan
d2bfefc3c1
proper max_records estimation for sort-repair of fulltext indexes
2004-10-29 14:24:06 +02:00
lenz@mysql.com
6b720d93be
- Applied some Windows portability fixes for myisampack.c and sql_handler.cc
...
(backports from fixes made in 4.1)
2004-10-27 21:51:27 +02:00
serg@serg.mylan
fb232f7e54
don't hang if the text contains illegal characters
2004-10-25 10:23:38 +02:00
serg@serg.mylan
66124a5ec1
Merge bk-internal.mysql.com:/home/bk/mysql-4.1/
...
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
2004-10-22 22:44:08 +02:00
serg@serg.mylan
9336d010af
correct fix for the bug #6151
2004-10-22 22:42:11 +02:00
lenz@mysql.com
0c3fb81a70
- applied portability fix for Windows (1ULL -> ULL(1)) to myisampack.c
2004-10-22 22:26:57 +02:00
serg@serg.mylan
1e60c59102
Merge bk-internal.mysql.com:/home/bk/mysql-4.1/
...
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
2004-10-22 20:34:25 +02:00
serg@serg.mylan
5d524d9e8e
Merge bk-internal.mysql.com:/home/bk/mysql-4.1/
...
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
2004-10-22 18:21:56 +02:00
monty@mysql.com
3afecef4df
Fix compiler warnings (detected by Intel's C++ compiler)
...
Fixed checking of privilege handling in CREATE ... SELECT (Bug #6094 )
2004-10-22 18:44:51 +03:00
serg@serg.mylan
0ad752e8af
s/puts/printf/
2004-10-21 15:34:26 +02:00
monty@mysql.com
e1218474b8
Merge with 4.0
2004-10-20 16:24:28 +03:00
monty@mysql.com
1f8b3d0f22
Code cleanups (done during review of new code)
...
Rename innodb_table_locks_old_behavior -> innodb_table_locks
Set innodb_table_locks to off by default to get same behaviour as in MySQL 4.0.20
(This means that Innodb ignore table locks by default, which makes it easier to combine MyISAM and InnoDB to simulate a transaction)
2004-10-20 11:24:08 +03:00
monty@mishka.local
04c23808a8
Review of all code pushed since last review
...
Simple optimzations and cleanups
Removed compiler warnings and fixed portability issues
Added client functions 'mysql_embedded()' to allow client to check if we are using embedded server
Fixes for purify
2004-10-20 01:28:42 +03:00
sergefp@mysql.com
d86b33c641
Merge spetrunia@bk-internal.mysql.com:/home/bk/mysql-4.0
...
into mysql.com:/mnt/tmp/mysql-4.0-bug-myisampack
2004-10-11 21:30:25 +04:00
monty@mysql.com
1dd4bd5f6c
Merge mysql.com:/home/my/mysql-4.0 into mysql.com:/home/my/mysql-4.1
2004-10-07 12:51:32 +03:00
monty@mysql.com
62f3cd6a31
Merge with 4.0 for 4.1 release
...
Noteworthy:
- New HANDLER code
- New multi-update-grant-check code
- Table lock code in ha_innodb.cc was not applied
2004-10-06 19:14:33 +03:00
monty@mysql.com
97febc4dc4
Code cleanups while doing review of pushed code
2004-10-06 17:20:39 +03:00
monty@mysql.com
c27d22b44e
Reverted patch for new usage of open_count as it caused more problems than it solved
...
Cleaned up patch for checking locks for multi-table updates
2004-10-06 01:24:21 +03:00
sergefp@mysql.com
f7b6a99d50
Fix for BUG#4785 part two:
...
* If at least one of indexes is disabled, use data file size as an estimate
for key file size.
* Added handling for joined tables.
2004-09-29 23:25:32 +04:00
sergefp@mysql.com
df267c6c0a
Merge spetrunia@bk-internal.mysql.com:/home/bk/mysql-4.0
...
into mysql.com:/mnt/tmp/mysql-4.0-bug-myisampack
2004-09-22 16:42:06 +04:00
sergefp@mysql.com
6e0ba8e615
Fix for BUG#4785:
...
* myisampack leaves key_file_length value from original table
* myisamchk uses this value when calculating key file pointer length
2004-09-22 16:29:15 +04:00
ingo@mysql.com
7afb03b7ed
bug#2831 - --extenral-locking does not fully work with --myisam-recover.
...
Changed the semantics of open_count so that it is decremented
at every unlock (if it was incremented due to data changes).
So it indicates a crash, if it is non-zero after a lock.
The table will then be repaired.
2004-09-18 20:33:39 +02:00
hf@deer.(none)
02595629c2
Fix for bug #5532 (error 22 inserting GIS data)
...
This bug is the result of weird error happening with mi_float8get and double
arythmetic. I described that in 'Bug that looks potentially dangerous' email
2004-09-15 19:46:42 +05:00
monty@mysql.com
31122efde7
Merge with 4.1
...
(Includes merge of arena code in 4.1 and 5.0)
2004-09-06 15:14:10 +03:00
serg@serg.mylan
9153fd2ae4
merged
2004-09-03 22:12:27 +02:00