[MEddy]

Kevin Sikes wrote on Oct 17 2008, 02:59 PM:

A situation like this is where best practices can guard against trouble. For instance, consider this command:

DELETE FROM SomeCriticalTable WHERE UserID=12345

If you start typing in natural order and get to this point when the query is unexpectedly submitted, you're in trouble! :

DELETE FROM SomeCriticalTable

It's better to put a stub in for the DELETE command and fill it in after your WHERE clause is complete:

DL FROM SomeCriticalTable WHERE UserID=12345

Once the WHERE clause is complete, go back to the beginning of the line and replace DL with DELETE. Now you'll get a harmless syntax error if your query is inadvertently submitted while you are constructing the rest of your query.

Kevin Sikes

Absolutely. I write select statements first and then convert them to deletes/updates when I'm sure everything is correct.

[MEddy]

I should have thought to try this in a different program. I have the execute buttons switched, so I use F5. I tried TextPad (where F5 is the shortcut for 'Find'), and sure enough the Find dialogue came up when I typed -09 several times in a row.

Thanks and sorry for the misunderstanding.

[Edit]

Just to clarify, it is actually mimicking 'F8' rather than 'F5', so it is trying 'Execute and Edit Results' in Yog, and bringing up the 'Replace' dialogue in TextPad.

I am using a Dell wired USB keyboard that came with a Dell workstation. It is Windows XP Pro SP3. I am using a standard Windows driver (version 5.1.2600.5512). I am using US English language setting.

It does not appear to be any issue with the Yog but rather with the keyboard or driver, most likely, so you are absolutely correct about this.

[MEddy]

I am sorry, allow me to clarify:

I would like to be able to 'Find Next' without having to bring up the 'Find' dialogue.

Thanks!

[MEddy]

adarsh wrote on Feb 22 2007, 04:11 PM:

Thanks for reporting.

we will go through this issue.

download 5.23 RC3 and try once.

is it HTTP connections?

No, they are all MySQL connections, done in about as normal a way as possible.

I have installed 5.23 RC3 and will post back if I have any problems. It might take awhile.

[MEddy]

Beta 10 just quietly crashed when I alt-tabbed to it. 🙁

I will try beta 11 now.

— edit —

Is beta 11 the same as RC 1? I am trying RC 1 now…

[MEddy]

It has only been about a week since I installed it, but beta 10 is working well so far. There have been 0 crashes, so things look much better than with the previous versions. I look forward to the official release with this fix.

Thanks for getting this fixed up.

[MEddy]

So far so good with beta 10 after a few days.

I will post an update again later.

[MEddy]

Didn't take long.

Using 5.2 beta 8:

It crashed when I alt-tabbed TO it from another application. It did not bring up anything asking me if I wanted to copy or save a dump of any kind. It did not generate a dump file anywhere that I can find. Windows did not show me the 'a program has crashed' dialogue box. It just disappeared quietly.

I had 2 connections open. I had just installed the program (to a new folder) and had just connected to 2 servers, so I am quite certain that neither connection had timed out yet. The only thing I did besides add 2 connections and open them was to turn off auto-complete. Total time between installation and crash was under 5 minutes.

[MEddy]

Sorry I haven't been keeping up to date with this thread. Regarding my setup:

Resolution: It happens with both 1024×768 and 1152×864

Using only one monitor.

Font: Normal

CPU: A single Pentium 4 3.0GHz, single core, without hyperthreading

OS: Windows XP Pro w/ SP2 (5.1, Build 2600)

It seems to happen regardless of the amount of data in my results pane. It does only seem to happen when I have more than 1 connection open. It happens when switching to the Yog, clicking the 'Window' menu and selecting a different connection, and maybe sometimes when switching away from the Yog (though I can't remember about the latter; the first 2 cases I mention are the most frequent).

I will install the latest build and see what happens.

[MEddy]

Ok, it happened to me when I clicked on the 'Window' menu and switched to a different connection.

[MEddy]

Downloading now; I will post here if it happens again.

By the way, I mentioned above that the problem has sometimes happened with only 1 connection open. I may be mistaken about that; since I posted that, it has only ever crashed when more than 1 connection was open.

Lastly, your link to the debug install is broken! Pretty easy to figure out what it should be, but not everyone will figure that out.

[MEddy]

I almost forgot to mention: I have also seen the problem occur when using the 'Window' menu to switch between open connections. I click on the 'Window' menu, click on one of the other windows listed, and the Yog just disappears.

Edit: Also, I can now confirm that the problem still occurs with the unreleased version that Peter posted on the first page of this thread.

[MEddy]

I also experienced the problem mentioned where the Yog would close itself. It happened several times per day. It would happen sometimes with only one connection open, sometimes with several connections open. It happened sometimes when it had been open for a few hours, and sometimes when it had been open less than an hour.

The problem seemed only to happen when I was trying to switch to the Yog when it was minimized or another window was active. It would happen sometimes when I alt-tabbed to it, and other times when I clicked on it on the windows taskbar. I'm not sure if it ever just closed itself when I wasnt even looking at it or trying to switch to it.

I downloaded the “5.2 (BETA) Full” from the downloads page on Oct 4. This is the version that has been giving me problems for the past week. This seems to be the same version that is still on the downloads page today: Beta 5.

[Author]

Posts