Suggestion For Upgrading Job Specs

[royvarley]

If this has already been reported, sorry, I did look.

I've upgraded from 5.0 to 5.2 which solved a small problem for me after I'd had to upgrade MySQL.

However, being the impatient sort that I am, I tested my overnight batch runs by trying them out using the GUI. And left the batch files as-is.

Next morning all sja runs had crashed. No error messages. Just the usual windows “do you want to send an error report” etc…

Turns out that the later verion of sja likes its templates to be updated. Fair enough… but:

Can we not have sja simply crash? An error message saying something like “Old version of template needs to be updated” or whatever would help frayed nerves.

And why not update the templates anyway during the run? All the information is there. Rename the old template to xxx.old and create a new template. And give us a little log message that tells us what's happened.

And I'd still like better logging in the log files. I don't just want to know about errors. I want to know what got changed during the run. Give us a “verbose” mode which tells us everything that's happened – and a not-so-verbose mode which lists the current on-screen summary into the log file.

bye now

[peterlaursen]

Quote:

Can we not have sja simply crash?

From next 5.21 beta SJA will use the same debugging concept as SQLyog GUI.

http://www.webyog.com/faq/32_145_en.html

Quote:

Give us a “verbose” mode

Is planned (due to user requests). Personally I do not understand why people want 100.000's of INSERT, UPDATE and DELETE statements.

I will return back with the 'old templates' issue. Nothing should crash with old job files. A few tags have been added, but if they are not there, defaults should be used. But I need to discuss details with developers.

[peterlaursen]

Confirmed that old job files should work.

Also we now can provide a pre-release build with this Debugging concept integrated in SJA if problem persists.

Also can you provide us with a test case?

[Author]

Posts