An error occurred fetching the project authors.
- 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.
-
- 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.
-
- 17 Aug, 2006 1 commit
-
-
jimw@rama.(none) authored
The problem was that the error handling was using a too-small buffer to print the error message generated. We fix this by not using a buffer at all, but by using fprintf() directly. There were also some problems with the error handling in table dumping that was exposed by this fix that were also corrected.
-
- 14 Aug, 2006 3 commits
-
-
brian@zim.(none) authored
-
kostja@bodhi.local authored
-
kostja@bodhi.local authored
-
- 10 Aug, 2006 1 commit
-
-
andrey@example.com authored
-
- 03 Aug, 2006 2 commits
-
-
tsmith@maint1.mysql.com authored
-
msvensson@neptunus.(none) authored
-
- 02 Aug, 2006 1 commit
-
-
grog@eucla.lemis.com authored
Quote PKEY.
-
- 29 Jul, 2006 1 commit
-
-
jimw@rama.(none) authored
-
- 24 Jul, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
- Add call to 'safe_exit' function when db query fails.
-
- 17 Jul, 2006 1 commit
-
-
iggy@rolltop.ignatz42.dyndns.org authored
-
- 14 Jul, 2006 1 commit
-
-
mysqldump did not select the correct database before trying to dump views from it. this resulted in an empty result set, which in turn startled mysql-dump into a core-dump. this only happened for views, not for tables, and was only visible with multiple databases that weren't by sheer luck in the order mysqldump required, anyway. this fixes by selecting the correct database before dumping views; it also catches the empty set-condition if it should occur for other reasons.
-
- 13 Jul, 2006 1 commit
-
-
mysqldump did not select the correct database before trying to dump views from it. this resulted in an empty result set, which in turn startled mysql-dump into a core-dump. this only happened for views, not for tables, and was only visible with multiple databases that weren't by sheer luck in the order mysqldump required, anyway. this fixes by selecting the correct database before dumping views; it also catches the empty set-condition if it should occur for other reasons.
-
- 07 Jul, 2006 1 commit
-
-
kostja@bodhi.local authored
-