An error occurred fetching the project authors.
  1. 15 Sep, 2008 1 commit
    • Patrick Crews's avatar
      Bug#37938 Test "mysqldump" lacks various INSERT statements / values · ef1d6cca
      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.
      ef1d6cca
  2. 02 Mar, 2008 1 commit
  3. 22 Feb, 2008 1 commit
    • anozdrin/alik@quad.'s avatar
      Fix for Bug#30217: Views: changes in metadata behaviour · 340906f4
      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.
      340906f4
  4. 13 Feb, 2008 1 commit
  5. 02 Nov, 2007 1 commit
  6. 03 Oct, 2007 1 commit
  7. 02 Oct, 2007 1 commit
  8. 01 Oct, 2007 1 commit
    • gshchepa/uchum@gleb.loc's avatar
      Fixed bug #31077. · 5fc81ee8
      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.
      5fc81ee8
  9. 05 Sep, 2007 1 commit
    • gshchepa/uchum@gleb.loc's avatar
      Fixed bug #29938. · adfbea36
      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.
      adfbea36
  10. 27 Jul, 2007 2 commits
    • anozdrin/alik@ibm.'s avatar
    • anozdrin/alik@ibm.'s avatar
      Fix for BUG#30027: mysqldump does not dump views properly. · e73f004f
      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.
      e73f004f
  11. 20 Jul, 2007 1 commit
    • gshchepa/uchum@gleb.loc's avatar
      Fixed bug #29788. · c3e925ee
      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.
      c3e925ee
  12. 18 Jul, 2007 1 commit
    • gshchepa/uchum@gleb.loc's avatar
      Fixed bug #28524. · 3f91aeda
      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.
      3f91aeda
  13. 07 Jun, 2007 1 commit
  14. 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
  15. 15 May, 2007 1 commit
  16. 01 May, 2007 1 commit
  17. 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
  18. 05 Apr, 2007 1 commit
  19. 02 Apr, 2007 1 commit
  20. 27 Mar, 2007 1 commit
  21. 26 Mar, 2007 1 commit
  22. 22 Mar, 2007 1 commit
  23. 19 Feb, 2007 2 commits
  24. 21 Nov, 2006 4 commits
  25. 15 Nov, 2006 1 commit
  26. 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
  27. 21 Sep, 2006 1 commit
  28. 18 Sep, 2006 1 commit
  29. 16 Sep, 2006 1 commit
  30. 15 Sep, 2006 1 commit
  31. 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
  32. 01 Sep, 2006 1 commit
  33. 29 Aug, 2006 1 commit
  34. 28 Aug, 2006 1 commit