An error occurred fetching the project authors.
- 15 Sep, 2008 1 commit
-
-
Patrick Crews authored
Moved fix for this bug to 5.0 as other mysqldump bugs seem tied to concurrent_insert being on Setting concurrent_insert off during this test as INSERTs weren't being completely processed before the calls to mysqldump, resulting in failing tests. Altered .test file to turn concurrent_insert off during the test and to restore it to whatever the value was at the start of the test when complete. Re-recorded .result file to account for changes to variables in the test.
-
- 02 Mar, 2008 1 commit
-
-
skozlov/ksm@mysql.com/virtop.(none) authored
-
- 22 Feb, 2008 1 commit
-
-
anozdrin/alik@quad. authored
between 5.0 and 5.1. The problem was that in the patch for Bug#11986 it was decided to store original query in UTF8 encoding for the INFORMATION_SCHEMA. This approach however turned out to be quite difficult to implement properly. The main problem is to preserve the same IS-output after dump/restore. So, the fix is to rollback to the previous functionality, but also to fix it to support multi-character-set-queries properly. The idea is to generate INFORMATION_SCHEMA-query from the item-tree after parsing view declaration. The IS-query should: - be completely in UTF8; - not contain character set introducers. For more information, see WL4052.
-
- 13 Feb, 2008 1 commit
-
-
sven@riska.(none) authored
This is *not* a fix to the bug. I'm only disabling the failing part of mysqldump.test until the bug is fixed. Whoever fixes it, please re-enable the test.
-
- 02 Nov, 2007 1 commit
-
-
gluh@mysql.com/eagle.(none) authored
db name should be quoted. this code does communication with the server. it's always ok to quote names in this case.
-
- 03 Oct, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
Bug #31077: post-commit fix.
-
- 02 Oct, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
Bug #31077: post-commit fix.
-
- 01 Oct, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
mysqldump adds the "-- Dump completed on YYYY-MM-DD hh:mm:ss" string to the end of output if the --comments switch is on. The only way to suppress this line is to use --skip-comments/--compact switch. New switch has been added to the mysqldump client command line: --dump-date. For the compatibility with previous releases, by default the --dump-date is on. The --dump-date switch forces mysqldump to add date to the "-- Dump completed on ..." string at the end of output. The --skip-dump-date switch supresses the output of date string and uses short form of that commentary: "-- Dump completed". --skip-comments or --compact switches disable the whole commentary as usual.
-
- 05 Sep, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
mysqldump --skip-events --all-databases dumped data of the mysqld.event table, and during the restoration from this dump events were created in spite of the --skip-events option. The mysqldump client has been modified to ignore mysql.event table data in case of --skip-events options.
-
- 27 Jul, 2007 2 commits
-
-
anozdrin/alik@ibm. authored
-
anozdrin/alik@ibm. authored
mysqldump generates view defitions in two stages: - dump CREATE TABLE statements for the temporary tables. For each view a temporary table, that has the same structure as the view is created. - dump DROP TABLE statements for the temporary tables and CREATE VIEW statements for the view. This approach is required because views can have dependencies on each other (a view can use other views). So, they should be created in the particular order. mysqldump however is not smart enough, so in order to resolve dependencies it creates temporary tables first of all. The problem was that mysqldump might have generated incorrect dump for the temporary table when a view has non-ASCII column name. That happened when default-character-set is not utf8. The fix is to: 1. Switch character_set_client for the mysqldump's connection to binary before issuing SHOW FIELDS statement in order to avoid conversion. 2. Dump switch character_set_client statements to UTF8 and back for CREATE TABLE statement that is issued to create temporary table.
-
- 20 Jul, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
After dumping triggers mysqldump copied the value of the OLD_SQL_MODE variable to the SQL_MODE variable. If the --compact option of the mysqldump was not set the OLD_SQL_MODE variable had the value of the uninitialized SQL_MODE variable. So usually the NO_AUTO_VALUE_ON_ZERO option of the SQL_MODE variable was discarded. This fix is for non-"--compact" mode of the mysqldump, because mysqldump --compact never set SQL_MODE to the value of NO_AUTO_VALUE_ON_ZERO. The dump_triggers_for_table function has been modified to restore previous value of the SQL_MODE variable after dumping triggers using the SAVE_SQL_MODE temporary variable.
-
- 18 Jul, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
For each view the mysqldump utility creates a temporary table with the same name and the same columns as the view in order to satisfy views that depend on this view. After the creation of all tables, mysqldump drops all temporary tables and creates actual views. However, --skip-add-drop-table and --compact flags disable DROP TABLE statements for those temporary tables. Thus, it was impossible to create the views because of existence of the temporary tables with the same names.
-
- 07 Jun, 2007 1 commit
-
-
msvensson@pilot.(none) authored
- Turn on binlog only for tests that need it - Skip those tests if --skip-binlog is used
-
- 25 May, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
sometimes `mysqldump --hex-blob' overruned output buffer by '\0' byte. The dump_table() function has been fixed to reserve 1 byte more for the last '\0' byte of dumped string.
-
- 15 May, 2007 1 commit
-
-
df@pippilotta.erinye.com authored
-
- 01 May, 2007 1 commit
-
-
tsmith@quadxeon.mysql.com authored
-
- 30 Apr, 2007 2 commits
-
-
mysqldump didn't properly handle getting no data on SHOW CREATE PROCEDURE. If S/C/P fails (due to dumping user's insufficient privileges on mysql.proc, say), mysqldump will print a comment to that effect to the output and return an error-code. If the -f (force) option is used, the dump will continue, otherwise, it will abort right there and then. Also fixes Bug#22761, "mysqldump reports no errors when using --routines without mysql.proc privileges" --- Merge mysql.com:/home/tnurnberg/27293/50-27293 into mysql.com:/home/tnurnberg/27293/51-27293 --- Merge tnurnberg@bk-internal.mysql.com:/home/bk/mysql-5.1-maint into mysql.com:/home/tnurnberg/27293/51-27293
-
mysqldump didn't properly handle getting no data on SHOW CREATE PROCEDURE. If S/C/P fails (due to dumping user's insufficient privileges on mysql.proc, say), mysqldump will print a comment to that effect to the output and return an error-code. If the -f (force) option is used, the dump will continue, otherwise, it will abort right there and then. Also fixes Bug#22761, "mysqldump reports no errors when using --routines without mysql.proc privileges" --- Merge tnurnberg@bk-internal.mysql.com:/home/bk/mysql-5.0-maint into mysql.com:/home/tnurnberg/27293/50-27293
-
- 05 Apr, 2007 1 commit
-
-
Kristofer.Pettersson@naruto. authored
- Giving the directive '--all-databases' to mysqldump caused an attempt to lock and dump log tables which don't support this operation. - With this patch the log tables are excluded from the set of databases tables to dump.
-
- 02 Apr, 2007 1 commit
-
-
iggy@recycle.(none) authored
-
- 27 Mar, 2007 1 commit
-
-
iggy@recycle.(none) authored
- mysqldump executes a SHOW CREATE VIEW statement to generate the text that it outputs. When the function name is retrieved it's database name is unconditionally prepended. This change causes the function's database name to be prepended only when it was used to define the function.
-
- 26 Mar, 2007 1 commit
-
-
opt_complete_insert was improperly used by accident. Use complete_insert flag instead.
-
- 22 Mar, 2007 1 commit
-
-
Damien@damiendev. authored
Fixes to buffer overlows from long command line args, and unchecked dyn_str return codes. Also light refactoring.
-
- 19 Feb, 2007 2 commits
-
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
-
- 21 Nov, 2006 4 commits
-
-
monty@mysql.com/nosik.monty.fi authored
Moved .progress files into the log directory Moved 'cluster' database tables into the MySQL database, to not have 'cluster' beeing a reserved database name Fixed bug where mysqld got a core dump when trying to use a table created by MySQL 3.23 Fixed some compiler warnings Fixed small memory leak in libmysql Note that this doesn't changeset doesn't include the new mysqldump.c code required to run some tests. This will be added when I merge 5.0 to 5.1
-
Moving tests to 4.1 section
-
Moving tests into their new place into 4.1 tests section
-
Backporting from 5.0
-
- 15 Nov, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
-
- 18 Oct, 2006 1 commit
-
-
iggy@rolltop.ignatz42.dyndns.org authored
The mysqldump command with both the --xml and --hex-blob options will output blob data encoded as hexBinary. The proper XML datatype is xs:hexBinary. The correct XML datatype is specified be setting the xsi_type attribute equal to xs:hexBinary for each encoded element.
-
- 21 Sep, 2006 1 commit
-
-
- 18 Sep, 2006 1 commit
-
-
mats@romeo.(none) authored
-
- 16 Sep, 2006 1 commit
-
-
- 15 Sep, 2006 1 commit
-
-
- 14 Sep, 2006 1 commit
-
-
iggy@rolltop.ignatz42.dyndns.org authored
Bug#21424 mysqldump failing to export/import views. Dumps are created for the tables in each specified database then for the views in each specified database. This bug occurs when any database's views depend on the mysql database's table data while being restored. Added command line option --flush-privileges to the mysqldump utility which causes a FLUSH PRIVILIGES statement to be written to the dump after the mysql database.
-
- 01 Sep, 2006 1 commit
-
-
jimw@rama.(none) authored
so that 4.1 and 5.0 tests are all in the right place and no tests are duplicated.
-
- 29 Aug, 2006 1 commit
-
-
iggy@rolltop.ignatz42.dyndns.org authored
-
- 28 Aug, 2006 1 commit
-
-
iggy@rolltop.ignatz42.dyndns.org authored
init_dumping now accepts a function pointer to the table or view specific init_dumping function. This allows both tables and views to use the init_dumping function.
-