An error occurred fetching the project authors.
  1. 03 Oct, 2006 1 commit
  2. 18 Sep, 2006 1 commit
  3. 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
  4. 01 Sep, 2006 2 commits
  5. 28 Aug, 2006 1 commit
  6. 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
  7. 14 Aug, 2006 1 commit
  8. 03 Aug, 2006 1 commit
  9. 02 Aug, 2006 2 commits
  10. 24 Jul, 2006 7 commits
  11. 17 Jul, 2006 1 commit
  12. 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
  13. 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
  14. 21 Jun, 2006 1 commit
  15. 06 Jun, 2006 1 commit
  16. 31 May, 2006 1 commit
    • tnurnberg@mysql.com's avatar
      Bug#18462: mysqldump does not dump view structures correctly · 8c243736
      tnurnberg@mysql.com authored
      (The above problem only occurs with -T -- create a separate file for
      each table / view.) This ChangeSet results in correct output of view-
      information while omitting the information for the view's stand-in
      table. The rationale is that with -T, the user is likely interested
      in transferring part of a database, not the db in its entirety (that
      would be difficult as replay order is obscure, the files being named
      for the table/view they contain rather than getting a sequence number).
      8c243736
  17. 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
  18. 29 May, 2006 2 commits
  19. 25 May, 2006 1 commit
  20. 19 May, 2006 1 commit
  21. 26 Apr, 2006 1 commit
  22. 24 Apr, 2006 2 commits
  23. 18 Apr, 2006 1 commit
    • msvensson@neptunus.(none)'s avatar
      Bug#17208 SSL: client does not verify server certificate · a51668c7
      msvensson@neptunus.(none) authored
       - Add new function 'ssl_verify_server_cert' which is used if we are 
         connecting to the server with SSL. It will compare the hostname in 
         the server's cert against the hostname that we used when connecting 
         to the server. Will reject the connection if hostname does not match.
       - Add new option "OPT_SSL_VERIFY_SERVER_CERT" to be passed to mysql_options
         which will turn on checking of servers cert.
       - Add new argument "ssl-verify-server-cert" to all mysql* clients which 
         will activate the above option.
       - Generate a new server cert with 1024 bits that has "localhost" as the server name.
      a51668c7
  24. 10 Mar, 2006 1 commit
  25. 09 Mar, 2006 1 commit
  26. 02 Mar, 2006 1 commit
    • anozdrin@mysql.com's avatar
      Implementation of WL#2897: Complete definer support in the stored routines. · fbb59203
      anozdrin@mysql.com authored
      The idea is to add DEFINER-clause in CREATE PROCEDURE and CREATE FUNCTION
      statements. Almost all support of definer in stored routines had been already
      done before this patch.
      
      NOTE: this patch changes behaviour of dumping stored routines in mysqldump.
      Before this patch, mysqldump did not dump DEFINER-clause for stored routines
      and this was documented behaviour. In order to get full information about stored
      routines, one should have dumped mysql.proc table. This patch changes this
      behaviour, so that DEFINER-clause is dumped.
      
      Since DEFINER-clause is not supported in CREATE PROCEDURE | FUNCTION statements
      before this patch, the clause is covered by additional version-specific comments.
      fbb59203
  27. 23 Feb, 2006 2 commits
  28. 21 Feb, 2006 1 commit
  29. 16 Feb, 2006 1 commit