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

Feature Req.: Assosciate Sql File With Connection

forums forums SQLyog SQLyog: Bugs / Feature Requests Feature Req.: Assosciate Sql File With Connection

  • This topic is empty.
Viewing 3 reply threads
  • Author
    Posts
    • #10060
      magge
      Member

      Sometimes I think it would be very useful to backtrack the last things I did using SQLyog. With current SQLyog versions I can save a SQL file and open it later on. But wouldnt it be great option if I could have that file automatically opened (filename provided in connection dialog – so it's one file per server?), and then I can just CTRL+S to save it without having to enter the filename again.

      Another option could be storing the history locally and then reload this in the history window.

      Perhaps this should somehow be per database instead of per server too?

      Just a suggestion. 😎

    • #23020
      peterlaursen
      Participant

      “..useful to backtrack the last things I did using SQLyog ..”

      What actually is needed is an option to save or 'spool' history to a file and load such file into SQLyog again.

      This is a planned feature. But it is 3rd priority only (of 5).

    • #23021
      magge
      Member

      Ok, I see. That's nice to know! 🙂

      While the history, the query window or a connection offcourse does not relate to a specific DB – it could maybe be nice to have a backlog per DB. But that would maybe break with fundamental rules of the SQLyog GUI ?

      I do suspect that it's more useful to see the latest actions on a specific DB rather than the latest actions on that server or the latest actions performed by SQLyog.

      I suppose details are not planned yet… 😛 Now you have my comments.

    • #23022
      peterlaursen
      Participant
      Quote:
      a backlog per DB

      Such feature should be implemented in the Server or the Storage Engine maybe.

      😛 .. Now you have my comments.

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