Unexpected Behavior: Execute Batch File

[mhsa]

Using version 3.5…

When I 'Execute Batch File', three things *don't* happen that I expect, and I'm not sure whether that is by design or not. They are:

• Statements are not logged to 'History' tab. The only exception I've found so far occurs when the script includes a 'use xxx;' statement. Those are logged to History as 'select database()' (internal SQLyog method?). I expected the individual statements to be logged to History.
• MySQL output is not logged to 'Messages' tab.
• Dataset(s) not displayed in the 'Results' tab.

Is there any effort to integrate the 'Execute Batch File' with the query window, etc.?

Thanks!

Zack

[Ritesh]

mhsa wrote on Jun 19 2003, 01:35 PM:

Using version 3.5…

When I 'Execute Batch File', three things *don't* happen that I expect, and I'm not sure whether that is by design or not. They are:

• Statements are not logged to 'History' tab. The only exception I've found so far occurs when the script includes a 'use xxx;' statement. Those are logged to History as 'select database()' (internal SQLyog method?). I expected the individual statements to be logged to History.
• MySQL output is not logged to 'Messages' tab.
• Dataset(s) not displayed in the 'Results' tab.

Is there any effort to integrate the 'Execute Batch File' with the query window, etc.?

Thanks!

Zack

All the three points are by design only. The Execute Batch File… option is used primarily to restore your database which is stored in SQL Scripts. The size of the file is limited by OS that can go in GBs, and SQLyog will execute all the SQL in the file without any performance penalty.

If you want to get all the message(s), result(s) etc. then you can open the file in the editor using File->Open… and execute all the queries by using Shift+F5 option.

HTH

[mhsa]

That's a shame 😉

As a data analyst, I have tons of canned queries. Such a feature would have saved several steps.

Perhaps you might consider renaming the option 'Restore Database' rather than 'Execute Batch File'. Since SQLyog adheres to the 'log everything' principle, this further confused me; I expected the batched statements to be logged, etc.

Oh, well. Thanks anyway!

[Author]

Posts