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

Feature: Day/week/month Query History

forums forums SQLyog SQLyog: Bugs / Feature Requests Feature: Day/week/month Query History

  • This topic is empty.
Viewing 3 reply threads
  • Author
    Posts
    • #9670
      Nick_Ring
      Member

      As a database programmer, I sometimes have debug things at the server level and sometimes it takes more than one day to figure out the problem.

      Would it be possible implement a history of the queries that I issued (from the Query tab, not what SQLyog generates), so if I need a query that I have forgotten to save, I can just pick it from my query history.

      What would be good if the history could be set out something like:

      + 2006 Jan

      + 2006 Feb

      : + 1st

      : + 2nd

      : :

      : +23rd

      :

      + 2006 May

      + Last Week

      + This Week

      + Yesterday

      + Today

      +

    • #21559
      peterlaursen
      Participant

      Well also queries that you issue yourself are logged to HISTORY as of now.

      Ther are some pending requests regarding HISTORY tab.

      * an option to 'switch off' the time information

      * HISTORY should (in my opinion) end each equery with a ';' – to make it easier re 're-use' it

      * an option to 'save' or 'spool' to a file. And to reload an olde history if needed.

      I think Ritesh promised to look into it in 5.2 or 5.3 release. Do you have a precise implementation idea? Some other program doing this as you would want SQLyog to do it (doesn't need to be a database client)?

    • #21560
      Ritesh
      Member

      Added for v5.3.

    • #21561
      Nick_Ring
      Member

      The only problem with the History tab is that is only relevant for the current session. Close that session or restart SQLyog and the history is cleared. Something more permanent and that can handle multiple sessions of SQLyog (not uncommon for me to have two or more open, working on different things) running at once.

      The 'global' history (which I will call it for now), should also place multiple queries (when selecting 'run all queries' or 'run selected query') in the global history as one entry so the whole sequence of commands are retrieved a once, which is slightly different to the (“session”) history does now – “session” history stores each one seperately so going back, it can be hard to figure would what was ran together and what wasn't.

      Reading the History tab requests, the last one is similar to what am I proposing. I wouldn't say I have a precise implmentation but something similar to MySQL Query Browser's implementation (has been a while since I have played around with it).

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