Forum Replies Created
-
AuthorPosts
-
S. LinesMember
Update:
I restored my hard drive to a backup that was a few weeks old. I tried sqlyog 64bit after the restore and it worked fine. I updated to the latest release of sqlyog and it worked fine.
So sometime between that backup and when I first tried the latest release of sqlyog something happened to my machine to cause the problem I am now having. I’m not sure what to do next.
32bit 9.2 does not have the problem on my laptop.
32bit 11.3.3-0.x86 does have the problem.
64bit 11.3.3-0.x64 does have the problem.
64bit 11.2.6-0.x64 used to work just fine, but stopped working after 11.3.3-0.x64 was installed.
Can you give me any clues regarding window resizing in Sqlyog Version 11 that is different than Sqlyog Version 9.2 that may give us a clue where to look?
S. LinesMemberThis save and restore is taking much longer than I anticipated. I will have to do it over the weekend.
S. LinesMemberHi Peter,
I will try the recommendations you suggested to try to get you more information.
The complete system freezes. Can not CTRL+ALT+DEL. Num lock does not toggle. Mouse does not move. The hard drive light does occasionally blink.
The only resolution to get out of this situation is a hard power down.
I’ll post more info when I get it.
S. LinesMemberThe 'table_open_cache' was set to 2000
The 'table_definition_cache' was set to 1400
After changing both of these to 16384, the error in the stored procedure DID NOT occur.
Thank you for your persistence in resolving this issue for me.
S. LinesMemberHello,
The SQL_MODE was set to no value.
I did run the statement: set sql_mode = ''
And then tried the call to the stored procedure again with the same result: “Prepared statement needs to be re-prepared”
S. LinesMemberSelect version() returns: 5.6.10
We are running version 11.11 64 bit of sqlyog
S. LinesMemberI've uploaded a small database that has a stored procedure. You can recreate this issue by calling the stored procedure.
S. LinesMemberHi,
Can you give us some insight into the issue, or when you may have a new release of sqlyog out?
We need to complete development of the stored procedure for a client.
Thanks,
Scott
S. LinesMemberIt is hard to read if you use /**/ as a commented out line.
The folding option “sees” the /* as the start of a comment, but doesn't see the */ on the same line. So it blocks out all lines until it “sees” the next */.
For example:
/**/
update tablea set blah = “”;
/**/
It treats this update statement as a commented out line when it really isn't.
'peterlaursen' wrote:There is no way to turn it off currently. But why is it 'hard to read' ?
-
AuthorPosts