monty@mysql.com
a1ab786091
Cleanups during review of code
...
Fixed newly introduced bug in rollup
2005-03-21 23:41:28 +02:00
gluh@gluh.mysql.r18.ru
b435d6e862
Merge 4.1 -> 5.0
2005-03-17 16:51:07 +03:00
lars@mysql.com
fc6eda1336
Fixes after Sinisa and Serg comments after push of patch for BUG#9123.
...
BUG#9123 is solved earlier than this patch though.
2005-03-16 21:56:56 +01:00
lars@mysql.com
52f190c098
BUG#9123: Updates after Mats review
2005-03-16 13:57:59 +01:00
lars@mysql.com
11f93ffd2d
Merge mysql.com:/home/bkroot/mysql-4.1 into mysql.com:/home/bk/b9123-4.1
2005-03-16 08:14:05 +01:00
reggie@mdk10.(none)
aa395b3a45
Merge mdk10.(none):/home/reggie/bk/mysql-4.1
...
into mdk10.(none):/home/reggie/bk/mysql-5.0
2005-03-15 11:42:31 -06:00
reggie@mdk10.(none)
887f2a53fe
Bug #6660 mysqldump creates bad pathnames on Windows
...
This is a modifiction of my previous patch after receiving feedback. This is a better way to fix the problem. With this patch, data directory and index directory will use only forward slashes (/) when on Windows.
mysqldump.c:
Removed fixPaths routine. Was improper fix for bug #6660
sql_show.cc:
Changed append_directory to convert backslashes to foward slashes when on Windows.
2005-03-15 11:33:06 -06:00
lars@mysql.com
26fae36137
BUG#9123: If a table name is given with an underscore,
...
then this must be properly quoted when sent to
SHOW TABLES LIKE ...
2005-03-15 16:23:02 +01:00
reggie@mdk10.(none)
75e1b9e765
Bug #6660 mysqldump creates bad pathnames on Windows
...
This really should not happen on Windows and part of the problem not fixed here is why show create table includes data directory when being run on Windows. However, this patch fixes the bug in mysqldump.c
mysqldump.c:
Added fixPaths function to convert \ to / in data directory and index directory entries only on Windows
2005-03-14 16:47:35 -06:00
serg@serg.mylan
956682de1a
merged
2005-03-09 14:09:06 +01:00
Sinisa@sinisa.nasamreza.org
79ac22e324
A fix for a bug #8830 , which occured when binary data from blob was
...
dumped with --hex-blob and --skip-extended-insert options.
2005-03-05 22:06:07 +02:00
monty@mysql.com
3839e443a4
merge with 4.1
2005-02-28 12:18:39 +02:00
bar@mysql.com
e42a8c454b
mysqldump.c:
...
Bug#7997 Add implicit --skip-set-charset when mysqldump from 4.0 server w/ 4.1 client
2005-02-25 18:12:53 +04:00
lars@mysql.com
7271a6014f
Merge 4.1->5.0
2005-02-22 22:40:34 +01:00
lars@mysql.com
1d3c67000b
BUG#6662: Changes after Guilhems and Sergs review
2005-02-22 12:40:31 +01:00
lars@mysql.com
be28ef0a20
BUG#6662: Importing mysqldumps should not show any warnings of level "notes".
2005-02-21 18:40:28 +01:00
monty@mysql.com
422c2eb868
4.1 -> 5.0 merge
2005-02-03 13:18:30 +02:00
monty@mysql.com
b87e0c52a7
Proper fix for comparision with ' '
...
(Bug #7788 "Table is full" occurs during a multitable update")
2005-02-01 16:27:08 +02:00
jimw@mysql.com
b7dda3f7c0
Merge
2005-01-31 16:27:17 -08:00
jimw@mysql.com
b4caa3aad5
Merge mysql.com:/home/jimw/my/mysql-4.1-8148
...
into mysql.com:/home/jimw/my/mysql-4.1-clean
2005-01-31 15:28:33 -08:00
reggie@bob.(none)
fc254d068f
Merge
2005-01-29 09:34:36 -06:00
reggie@bob.(none)
9af0b70d9e
Bug #5185 mysqldump for windows database gets table names with different case
...
mysqldump.c:
Trimmed some lines to be less than 80 chars. Using just NAME_LEN now for table name buffers
2005-01-29 09:25:56 -06:00
jimw@mysql.com
71670605ac
Use single quotes to set SQL_MODE in mysqldump output in case ANSI_QUOTES
...
was already defined on the server the dump is loaded into. (Bug #8148 )
2005-01-28 11:16:49 -08:00
reggie@bob.(none)
e9e4d936dc
Bug #5185 mysqldump for windows database gets table names with different case
...
Added the get_actual_table_name function that issues a SHOW TABLES LIKE '%s'. This will get the table
name in the proper case. We use this table name rather than the one given on the command line. This will
prevent problems when importing SQL on Linux that was generated on a Windows platform where case can be
an issue.
mysqldump.c:
call get_actual_table_name to get the table name in the proper case
2005-01-27 14:48:26 -06:00
serg@serg.mylan
c76405a7ee
merged
2005-01-24 19:41:42 +01:00
serg@serg.mylan
67ba2e367a
fixes/cleanups according to Coverity report
2005-01-24 15:48:25 +01:00
monty@mysql.com
502ba93b38
Merge with global tree
2005-01-18 04:03:26 +02:00
paul@kite-hub.kitebird.com
3b9c5f3a17
mysqldump.c:
...
Move out-of-order option.
2005-01-17 00:09:47 -06:00
guilhem@mysql.com
05793bb9b9
Merge
2005-01-16 21:39:21 +01:00
guilhem@mysql.com
84bc0db087
Fix for BUG#7850: force the transaction isolation level to REPEATABLE READ when --single-transaction
2005-01-13 00:44:13 +01:00
jimw@mysql.com
5010be1d8b
Merge mysql.com:/home/jwinstead2/mysql-4.1-clean
...
into mysql.com:/home/jwinstead2/mysql-5.0
2005-01-06 21:39:57 +01:00
bell@sanja.is.com.ua
d944dc9a78
postreview changes
2005-01-06 20:47:08 +02:00
bell@sanja.is.com.ua
779c33a5e7
fixed comparation with string constant on some platform (BUG#7651)
2005-01-06 19:13:58 +02:00
serg@sergbook.mysql.com
a04fc26c54
manually merged
2004-12-31 15:26:24 +01:00
serg@serg.mylan
cf6e2214d8
client/mysqldump.c
...
compilation failure fixed
cleanup
2004-12-28 17:33:49 +01:00
lars@mysql.com
967fac4ef6
WL#2319 V2: Exclude tables from dump
...
- Added a hash to keep track of database-table pairs.
- Specified database-table tables do not get dumped
2004-12-27 19:10:30 +01:00
bar@mysql.com
e53b446a73
Bug#7020: mysqldump --compatible=mysql40 still dumps in UTF8
...
See mysqldump.test comments for more details
2004-12-22 16:02:27 +04:00
monty@mishka.local
4f4bbfc279
Merge with 4.1
2004-12-22 13:54:39 +02:00
guilhem@mysql.com
884663662b
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).
2004-12-17 23:37:43 +01:00
gluh@gluh.mysql.r18.ru
58e75f6f24
fix according to review
2004-12-10 18:25:12 +03:00
gluh@gluh.mysql.r18.ru
2e912bbbe8
Don't display 'usage' privilege in TABLE_PRIVILEGES if we have columns privileges
...
mysqldump skips information_schema db
'use' now can use information_schema db
changed value of column 'Null' to 'NO' if column is not nullable
2004-12-10 12:07:11 +03:00
monty@mysql.com
b68f2307e0
Merge bk-internal.mysql.com:/home/bk/mysql-4.1
...
into mysql.com:/home/my/mysql-4.1
2004-12-09 12:50:37 +02:00
monty@mysql.com
01e4740f4c
Ensure that we free memory used with --order-by-primary (in mysqldump)
...
Simple, non critical, fix to mysql_fix_privilege_tables
2004-12-09 12:47:20 +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
9c23871867
help text corrected
2004-12-04 10:06:38 +01:00
tsmith@build.mysql.com
88f48f33c5
Merge bk-internal:/home/bk/mysql-4.1
...
into build.mysql.com:/users/tsmith/m/41/b
2004-12-02 15:33:12 +01:00
brian@avenger.(none)
b85f4677d5
Merge for Matt for Innodb bug.
2004-11-30 10:10:40 -08:00
ram@gw.mysql.r18.ru
0ca8fd2ee9
Merge rkalimullin@bk-internal.mysql.com:/home/bk/mysql-4.1
...
into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b6101
2004-11-30 12:27:17 +04:00