An error occurred fetching the project authors.
  1. 15 Nov, 2006 2 commits
  2. 18 Oct, 2006 2 commits
  3. 21 Sep, 2006 1 commit
  4. 20 Sep, 2006 1 commit
  5. 18 Sep, 2006 1 commit
  6. 15 Sep, 2006 1 commit
  7. 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
  8. 01 Sep, 2006 2 commits
  9. 29 Aug, 2006 1 commit
  10. 28 Aug, 2006 1 commit
  11. 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
  12. 14 Aug, 2006 3 commits
  13. 10 Aug, 2006 1 commit
  14. 03 Aug, 2006 3 commits
  15. 02 Aug, 2006 1 commit
  16. 29 Jul, 2006 1 commit
  17. 27 Jul, 2006 1 commit
    • anozdrin/alik@booka.'s avatar
      Fix for BUG#16211: Stored function return type for strings is ignored. · b7f403b5
      anozdrin/alik@booka. authored
      Fix for BUG#16676: Database CHARSET not used for stored procedures
      
      The problem in BUG#16211 is that CHARSET-clause of the return type for
      stored functions is just ignored.
      
      The problem in BUG#16676 is that if character set is not explicitly
      specified for sp-variable, the server character set is used instead
      of the database one.
      
      The fix has two parts:
      
        - always store CHARSET-clause of the return type along with the
          type definition in mysql.proc.returns column. "Always" means that
          CHARSET-clause is appended even if it has not been explicitly
          specified in CREATE FUNCTION statement (this affects BUG#16211 only).
      
          Storing CHARSET-clause if it is not specified is essential to avoid
          changing character set if the database character set is altered in
          the future.
      
          NOTE: this change is not backward compatible with the previous releases.
      
        - use database default character set if CHARSET-clause is not explicitly
          specified (this affects both BUG#16211 and BUG#16676).
      
          NOTE: this also breaks backward compatibility.
      b7f403b5
  18. 24 Jul, 2006 1 commit
  19. 19 Jul, 2006 1 commit
  20. 17 Jul, 2006 1 commit
  21. 14 Jul, 2006 3 commits
  22. 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
  23. 03 Jul, 2006 1 commit
  24. 21 Jun, 2006 2 commits
  25. 19 Jun, 2006 1 commit
  26. 15 Jun, 2006 1 commit
  27. 31 May, 2006 2 commits
  28. 30 May, 2006 1 commit
    • tnurnberg@mysql.com's avatar
      Bug#17371: Unable to dump a schema with invalid views · c7ae355d
      tnurnberg@mysql.com authored
      'show create' works even on views that are short of a base-table (this
      throw a warning though, like you would expect). Unfortunately, this is
      not what mysqldump uses; it creates stand-in tables and hence requests
      'show fields' on the view which fails with missing base-tables.  The
      --force option prevents the dump from stopping at this point; furthermore
      this patch dumps a comment showing create for the offending view for
      better diagnostics. This solution was confirmed by submitter as solving
      their/clients' problem. Problem might become non-issue once mysqldump no
      longer creates stand-in tables.
      c7ae355d
  29. 29 May, 2006 1 commit