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

Sticky Location For Log On Scheduled Jobs

forums forums SQLyog SQLyog: Bugs / Feature Requests Sticky Location For Log On Scheduled Jobs

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • #29191
      peterlaursen
      Participant

      1)

      ok .. Let us discuss request for 'sticky log position'. The logfile and sessionfile settings are not saved in jobfile. That would be one option. Another option would be to save in sqlyog.ini so that same setting as last time you executed a wizard will take effect if not changed by user (I thought it did now, but I will check). I do not quite understand if you request first or second?

      2)

      *connection details* do show, but *connection name* does not in my understanding. Do we agree? The connection name not is saved to the jobfile. Two reasons: 1) SJA does not need it – *connection name* is only relevant for the SQLyog GUI 2) It would be dangerous as the *details* for a *name* may change. That would create an ambiguous situation. What is stored in jobfile is the details that the client needs to send to the server to be able to connect. But as *name* not stored in jobfile it cannot display either when opening a jobfile.

    • #29192
      navyashree.r
      Member
      Quote:
      1)

      ok .. Let us discuss request for 'sticky log position'. The logfile and sessionfile settings are not saved in jobfile. That would be one option. Another option would be to save in sqlyog.ini so that same setting as last time you executed a wizard will take effect if not changed by user (I thought it did now, but I will check). I do not quite understand if you request first or second?

      Hi,

      Presently, whether its a new job or saved job it takes the default path 'Application Data' folder path.

      The request “Saving 'SJA Log' Location in Preferences” already in our tracker,

      http://code.google.com/p/sqlyog/issues/detail?id=1108

      Thank You.

      Regards,

      Navya

    • #29193
      peterlaursen
      Participant

      but maybe request was the -l and -s parameter values could optionally be stored in the job.xml?

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