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

Default options for SQLyog "export as script"

forums forums SQLyog SQLyog: Bugs / Feature Requests Default options for SQLyog "export as script"

  • This topic is empty.
Viewing 4 reply threads
  • Author
    Posts
    • #16541
      peterlaursen
      Participant

      I don't agree.

      But of course it's very unfortunate that you lose data. But it's the very common way to do things. MySQLAdministrator does the samme as well as the backup utilities for popular forum's software such as phpBB2, and other clients that I know.

      If you are running the scirpt the base is “reset” to the state it was, when the script was created. You could use the “syncronize” function instead – provided that you have another MySQL installation each table has a Primary Key.

    • #16542
      Ritesh
      Member

      Everybody has different requirements.

      SQLyog keeps track of last selected options. So once you uncheck it, it will start off with those options unchecked everytime. 😀

    • #16543
      patrickq
      Member

      Let me try to make my point once again (and I promise I'll stop there :-)):

      1. I don't think it can ever make sense to create a script which you know at the time it is created that it will not run successfully. This is doubly true when that same script starts its life by dropping the table which it will then fail to restore …

      2. More to the point: note that MySQLDump is apparently aware of the limitation on MySQL statement length. As a result, if you run mysqldump with default options, it too will generate long INSERT statements, BUT (and here comes the major difference) only as long as the net_buffer_length parameter. This parameter defaults to 1047551 so the result for each table is a series of INSERT statements each of that length or less, and the script works.

      If I may, I suggest that you indeed keep the default options as they are, if you think it's the best default for most users, but internally limit the length of each statement to what MySQL allows.

    • #16544
      Shadow
      Member

      It's the max_allowed_packet variable that controls the max allowed length of an insert statement. It could be a major enhancement, if SQLyog recognized this variable while loading data from script files.

    • #16545
      marcospc
      Member

      Unchecking the bulk option for batch scripts is actually a pain in the ass. Have you tried to insert 250K rows one by one? I think this needs serious modification. Uncheking the option might be worth it for a very few number of cases.

      M.

Viewing 4 reply threads
  • You must be logged in to reply to this topic.