[Igor]

peterlaursen wrote on Aug 15 2007, 01:08 PM:

“I am talking about opening the file I double click on, not pasting the statement”

Now what I figured was that if you choose to associate .sql files with SQLyog and doubleclick such file, the SQLyog will open and the content of the file will be displayed in the editor. It SQLyog is allready open then the new file would open in a new tab in the currently selected connection. Do we agree?

Yes, though I sometimes run multiple instances of Yog at the same time. But I guess the last one open will be OK. Or you can just launch a new one. Preference?

peterlaursen wrote on Aug 15 2007, 01:08 PM:

The only problem is that no connection is open if the program is not open (and then no Query Tab is open either), but of course we can 'push in between' a connections dialogue.

Yes, either that or (something you may want to implement in the future) just opening the file without having to connect to db at all. Then when you choose to do something with db, such as browse or deploy the stored proc in – you can bring up the connection dialog.

I found this feature missing when I was working offline and still wanted to edit the file in SQL Yog, but I couldn't because it wouldn't open up without a db connection.

I was one of the developers of SQL Station – and we had to deal with exactly the same issues…

Great job on the product!!!

[Igor]

peterlaursen wrote on Aug 15 2007, 12:54 AM:

No you are not doing anything wrong.

Association will start the program, but the statement will neither be exectued nor will the statement be pasted into the editor.

Thank for the idea. We will try to implement as soon as possible!

Great!

Just to clarify – I am talking about opening the file I double click on, not pasting the statement. Pretty much the same thing you can do now with ctrl+o.

Thanks!

[Igor]

Sorry, will do.

This was for 5.18. I can't reproduce it in 5.19 any more. So it seems that it is now fixed.

[Igor]

OK, cool, thanks!

Just to add here – this kind of browser experience became an industry standard of sorts – SQL Station, SQL Navigator, PL/SQL Developer, SQL Server UI tool – all use the same folder paradigm.

So this would be more familiar for people who (like me) migrate from Oracle or SQL Server to MySQL.

End of the year is great though!

Thanks again.

Igor.

[Igor]

peterlaursen wrote on Sep 5 2006, 08:18 PM:

I am sorry to disappoint you.

… but 'Viborg' is not 'Vyborg'. 'Vyborg is an old Swedish/Finnish spelling of 'Viborg'. Viborg is in Denmark and Vyborg is located close to the Finnish/Russian border.

Vi or Vy means 'holy/sacred place' in the ancient nordic language spoken at the time of the Viking Era. Viborg probably was the most important religious place in Denmark before christianity arrived!

You are not disappointing me. I knew that you were in Denmark and that the cities are different. I was in Denmark myself last summer (not in Jutland though). Have fun!

[Igor]

Peter, thanks for your quick replies!!!

I am in US, San Francisco Bay Area, so yeah, we use English localization of Windows. We need to have unicode, not just cyrillic. Cyrillic was just an example of one of my CDs, as well… I am from over there! BTW, Vyborg a city very close to the one I am from – St. Petersburg! 🙂 But this is of course different Vyborg – the one on Finnish border.

So I'll be waiting for your unicode release!

Thanks again for your help!

Igor.

PS. About 10 years ago by now I was one of three developers who did one of the first IDEs for Oracle – Platinum SQL Station. So am very much familiar with the problems you are facing…

[Igor]

peterlaursen wrote on Sep 5 2006, 07:40 PM:

Starting from SQLyog 5.17 we do use the same DELIMITER format as the programs from MySQL AB.

Please refer to: http://webyog.com/faq/33_7_en.html

What is the version you are using?

But this:

.. is not true. there is NO STANDARD for the DELIMITER syntax at all! The DELIMITER statement is NOT an SQL statement and it is not sent to the server! It is implemented in the client only. The purpose of the DELIMITER statement is that is shall be possible to distinguish whether a ';' (semicolon) seperates SQL-statements or not. It would be fairly possible for a graphical client to use coloring, indentation, or different fonts or whatever for this!

But we did – after multiple requests – adopt the syntax from MySQL AB in SQLyog 5.17!

Great, thanks!

Yes, I was using 5.15. I'll certainly download the latest.

I understand that DELIMITER is not a server side command, in fact, hopefully we won't need it soon in MySQL at all, as the parser should get smart enough to not need it. Oracle doesn't use it, SQL Server doesn't use it and they somehow know how to destinguish statements within stored proc vs. ones outside…

Anyway, I am glad you did this as otherwise automatic file deployments through the command line (and this is coming directly from AB, so nothing we can do about this one! :o) ) would be tricky (I was planning on parsing it out before deployment and just have DELIMITERs before and after the whole block of sps, but here you made my life easier, so thanks again!).

Best.

Igor.

[Author]

Posts