Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Difference In Options Between Sql Dump Functions

forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Difference In Options Between Sql Dump Functions

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • November 11, 2010 at 8:49 am #12151
      larsen
      Participant

      Hi,

      I noticed that the dialog for “Backup table as SQL dump” has more options than the icon for “Export as…” that can be used to create a sql dump for a custom query. Perhaps you could make it possible to also include those options in the “export as” dialog when the user chooses SQL as the output format. Or otherwise allow using custom queries for the “Backup table as SQL dump” dialog.

      Lars

    • November 11, 2010 at 9:11 am #31510
      peterlaursen
      Participant

      We deliberately did as we did with 'export as sql'.  This was never intended for backing up tables (if you try you get a warning), but to export a result set.  Result sets may come from different tables using different engines etc.

      We use the client API export_set function (http://dev.mysql.com/doc/refman/5.0/en/string-functions.html#function_export-set) to get the information (that means the data structure – as held by the client – of the result set alone to compose the table definition. (and BTW: I have an open bug report about same here: http://bugs.mysql.com/bug.php?id=58028)

      What are the specific options  you feel are missing?

    • November 11, 2010 at 11:09 am #31511
      larsen
      Participant

      I´m not really missing anything, but thought that the options should be consistent. In case this was done on purpose, I´m fine with it =)

  • Author
    Posts
Viewing 2 reply threads
  • You must be logged in to reply to this topic.