An error occurred fetching the project authors.
- 11 Sep, 2008 1 commit
-
-
Tatiana A. Nurnberg authored
mysqldump creates stand-in tables before dumping the actual view. Those tables were of the default type; if the view had more columns than that (a pathological case, arguably), loading the dump would fail. We now make the temporary stand-ins MyISAM tables to prevent this.
-
- 12 Mar, 2008 1 commit
-
-
cmiller@zippy.cornsilk.net authored
databases from 4.0 server mysqldump treated a failure to set the results charset as a severe error. Now, don't try to set the charset for the SHOW CREATE TABLE statement, if remote server's version is earlier than 4.1, which means it doesn't support changing charsets.
-
- 07 Mar, 2008 1 commit
-
-
gkodinov/kgeorge@magare.gmz authored
--master-data No error code was returned by mysqldump if it detects that binary logging is not enabled on the server. Fixed by returning error code.
-
- 20 Nov, 2007 1 commit
-
-
guilhem@gbichot4.local authored
this has already been closed by a note in the manual, now we complete this by a note in "mysqldump --help"
-
- 04 Oct, 2007 1 commit
-
-
tnurnberg@sin.intern.azundris.com authored
The combination of --single-transaction and --master-data requires START TRANSACTION WITH CONSISTENT SNAPSHOT which is available from mysqld 4.1 on. When trying this against an older server, print diagnostic, then, if --force is not given, abort. No test-case given since it would require a mysqld < 4.1.
-
- 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.
-
- 13 Sep, 2007 1 commit
-
-
make sure that if builder configured with a non-standard (!= 3306) default TCP port that value actually gets used throughout. if they didn't configure a value, assume "use a sensible default", which will be read from /etc/services or, failing that, from the factory default. That makes the order of preference - command-line option - my.cnf, where applicable - $MYSQL_TCP_PORT environment variable - /etc/services (unless configured --with-tcp-port) - default port (--with-tcp-port=... or factory default)
-
- 31 Aug, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
When dumping database from a 4.x server, the mysqldump client inserted a delimiter sign inside special commentaries of the form: /*!... CREATE DATABASE IF NOT EXISTS ... ;*/ During restoration that dump file was splitten by delimiter signs on the client side, and the rest of some commentary strings was prepended to following statements. The 4x_server_emul test case option has been added for use with the DBUG_EXECUTE_IF debugging macro. This option affects debug server builds only to emulate particular behavior of a 4.x server for the mysqldump client testing. Non-debugging builds are not affected.
-
- 25 Jul, 2007 1 commit
-
-
anozdrin/alik@ibm. authored
binary SHOW CREATE TABLE or SELECT FROM I_S. The problem is that mysqldump generates incorrect dump for a table with non-ASCII column name if the mysqldump's character set is ASCII. The fix is to: 1. Switch character_set_client for the mysqldump's connection to binary before issuing SHOW CREATE TABLE statement in order to avoid conversion. 2. Dump switch character_set_client statements to UTF8 and back for CREATE TABLE statement.
-
- 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.
-
- 28 Jun, 2007 1 commit
-
-
msvensson@pilot.(none) authored
- Move the check of too long path to 'get_one_option'
-
- 30 May, 2007 1 commit
-
-
tsmith@quadxeon.mysql.com authored
Fix harmless typo (caught thanks to warning)
-
- 27 May, 2007 1 commit
-
-
dkatz@damien-katzs-computer.local authored
fixed by using flush logs, dumping, then doing PURGE MASTER LOGS TO 'binfile', instead of deleting the log files at the beginning. NOTE: previously the delete-master-logs would reset the log names back to filename.00001. Now the trailing number doesn't get reset. This may need to be documented.
-
- 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.
-
- 16 May, 2007 1 commit
-
-
msvensson@pilot.blaudden authored
- mysqldump generated output that set OLD_SQL_MODE twice, to different values (for triggers), or not at all (for routines) in some cases.
-
- 30 Apr, 2007 1 commit
-
-
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
-
- 27 Mar, 2007 1 commit
-
-
jani@ua141d10.elisa.omakaista.fi authored
-
- 26 Mar, 2007 1 commit
-
-
opt_complete_insert was improperly used by accident. Use complete_insert flag instead.
-
- 23 Mar, 2007 2 commits
-
-
dkatz/Damien@damiendev. authored
Added some fixes for an existing memory leak and unitilialized variables, both caught by gcc.
-
tnurnberg@sin.intern.azundris.com authored
give some leeway on required permissions for SHOW FIELDS on views so an unknonwn DEFINER will no longer break mysqldump
-
- 22 Mar, 2007 2 commits
-
-
jani@ua141d10.elisa.omakaista.fi authored
-
Damien@damiendev. authored
Fixes to buffer overlows from long command line args, and unchecked dyn_str return codes. Also light refactoring.
-
- 22 Feb, 2007 1 commit
-
-
monty@mysql.com/narttu.mysql.fi authored
Fixed a couple of usage of not initialized warnings (unlikely cases)
-
- 23 Dec, 2006 1 commit
-
-
kent@mysql.com/kent-amd64.(none) authored
Changed header to GPL version 2 only
-
- 14 Dec, 2006 1 commit
-
-
monty@mysql.com/narttu.mysql.fi authored
- Removed not used variables and functions - Added #ifdef around code that is not used - Renamed variables and functions to avoid conflicts - Removed some not used arguments Fixed some class/struct warnings in ndb Added define IS_LONGDATA() to simplify code in libmysql.c I did run gcov on the changes and added 'purecov' comments on almost all lines that was not just variable name changes
-
- 30 Nov, 2006 2 commits
-
-
monty@mysql.com/narttu.mysql.fi authored
Don't assert if my_thread_end() is called twice (common case)
-
monty@mysql.com/narttu.mysql.fi authored
Fixed compiler warnings (detected by VC++): - Removed not used variables - Added casts - Fixed wrong assignments to bool - Fixed wrong calls with bool arguments - Added missing argument to store(longlong), which caused wrong store method to be called.
-
- 23 Nov, 2006 1 commit
-
-
monty@mysql.com/nosik.monty.fi authored
Fixed that --valgrind works again with mysql-test-run.sh Extended error messages when loosing connection during mysql_real_connect()
-
- 21 Nov, 2006 1 commit
-
-
Backporting from 5.0
-
- 20 Nov, 2006 1 commit
-
-
monty@mysql.com/nosik.monty.fi authored
(Mostly in DBUG_PRINT() and unused arguments) Fixed bug in query cache when used with traceing (--with-debug) Fixed memory leak in mysqldump Removed warnings from mysqltest scripts (replaced -- with #)
-
- 24 Oct, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
-
- 19 Oct, 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.
-
- 03 Oct, 2006 1 commit
-
-
iggy@rolltop.ignatz42.dyndns.org authored
-
- 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 2 commits
-
-
msvensson@neptunus.(none) authored
-
jimw@rama.(none) authored
so that 4.1 and 5.0 tests are all in the right place and no tests are duplicated.
-
- 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.
-