An error occurred fetching the project authors.
  1. 07 Jun, 2007 1 commit
  2. 25 May, 2007 1 commit
    • gshchepa/uchum@gleb.loc's avatar
      Fixed bug #28522: · 2ee30b0b
      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.
      2ee30b0b
  3. 01 May, 2007 1 commit
  4. 30 Apr, 2007 2 commits
    • tnurnberg@mysql.com/blasphemy.mysql.com's avatar
      Bug#27293: mysqldump crashes when dumping procedure defined by different user · 205dfa44
      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
      205dfa44
    • tnurnberg@mysql.com/blasphemy.mysql.com's avatar
      Bug#27293: mysqldump crashes when dumping procedure defined by different user · ce1074f6
      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
      ce1074f6
  5. 05 Apr, 2007 1 commit
  6. 02 Apr, 2007 1 commit
  7. 27 Mar, 2007 1 commit
  8. 26 Mar, 2007 1 commit
  9. 22 Mar, 2007 1 commit
  10. 19 Feb, 2007 2 commits
  11. 21 Nov, 2006 4 commits
  12. 15 Nov, 2006 1 commit
  13. 18 Oct, 2006 1 commit
    • iggy@rolltop.ignatz42.dyndns.org's avatar
      Bug#19745: mysqldump --xml produces invalid xml · 3c31c842
      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.
      3c31c842
  14. 21 Sep, 2006 1 commit
  15. 18 Sep, 2006 1 commit
  16. 16 Sep, 2006 1 commit
  17. 15 Sep, 2006 1 commit
  18. 14 Sep, 2006 1 commit
    • iggy@rolltop.ignatz42.dyndns.org's avatar
      Bug#21424 mysqldump failing to export/import views. ... · 4fa6c8c7
      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.
      4fa6c8c7
  19. 01 Sep, 2006 1 commit
  20. 29 Aug, 2006 1 commit
  21. 28 Aug, 2006 1 commit
  22. 17 Aug, 2006 1 commit
    • jimw@rama.(none)'s avatar
      Bug #21288: mysqldump segmentation fault when using --where · abc14800
      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.
      abc14800
  23. 14 Aug, 2006 3 commits
  24. 10 Aug, 2006 1 commit
  25. 03 Aug, 2006 2 commits
  26. 02 Aug, 2006 1 commit
  27. 29 Jul, 2006 1 commit
  28. 24 Jul, 2006 1 commit
  29. 17 Jul, 2006 1 commit
  30. 14 Jul, 2006 1 commit
    • tnurnberg@mysql.com/salvation.intern.azundris.com's avatar
      Bug#21014: Segmentation fault of mysqldump on view · 00ec3973
      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.
      00ec3973
  31. 13 Jul, 2006 1 commit
    • tnurnberg@mysql.com/salvation.intern.azundris.com's avatar
      Bug#21014: Segmentation fault of mysqldump on view · 4316f715
      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.
      4316f715
  32. 07 Jul, 2006 1 commit