[ronjeremy_69]

I’d just like to make yet another annual bump to this from over 3 years ago. I did not renew my license this year, and will not until this feature has been added.

[ronjeremy_69]

I'd just like to bump this from over 2 years ago. I just purchased a license renewal in hopes this feature has been added, but sadly it has not. Please make it so the left column can be set to a fixed or dynamic width — anything other than a percentage based on the current application width…

[ronjeremy_69]

That sounds great please keep us updated. Thanks!

[ronjeremy_69]

I would imagine it is possible. If you think about it, the left frame showing databases in SQLyog is the equivalent of the left frame containing the directory tree in Windows Explorer. If you test the behavior in Windows Explorer, you will notice that the left frame stays the same size no matter how big or small you make the application. SQLyog should also behave like this.

[ronjeremy_69]

peterlaursen wrote on Feb 11 2009, 11:17 AM:

Is it so bad to type 'se' or 'sel' ?

Yes! When you're sometimes typing hundreds of select statements daily, it really adds up being able to s[tab]=SELECT f[tab]=FROM w[tab]=WHERE

peterlaursen wrote on Feb 11 2009, 11:17 AM:

1) One more indexed column ('priority') in the kewords table and we will then be able to 'ORDER BY priority, keyword'. But then it will NOT appear between 'security' and 'sensitive'. What say about this?

no problem at all!

peterlaursen wrote on Feb 11 2009, 11:17 AM:

2) It could be added twice of course with both 'high' and 'low' priority. It could be two databases (a high' and a 'low' priority) what would make it posssible for user to have his own 'high priority' database.

This would work just as well.

peterlaursen wrote on Feb 11 2009, 11:17 AM:

Also tell: do you request this for TAB-inserts only or also for CTRL+ENTER and CTRL+SPACE? Also wnat 'high priority' keywords listed on top of those?

I guess TAB-inserts only since i never really use CTRL+ENTER or CTRL+SPACE.

One other “hack” i have found is an excellent time saver, is using sqlite3 to add a trailing space after most keywords.

update objects set object_name = object_name || ' ' where object_name = 'select';

update objects set object_name = object_name || ' ' where object_name = 'from';

update objects set object_name = object_name || ' ' where object_name = 'where';

This really makes typing queries that much more effiecint.

For example “SELECT price FROM items WHERE id > 10;”

Can be typed with “s[tab]price f[tab]items w[tab]id > 10;”

In the above, having trailing spaces automatically appear after SELECT, FROM, and WHERE saves you three keystrokes.

In fact, there will NEVER be a situation where there is NOT a trailing space after any of the aforementioned keywords, so this might be something to add to SQLyog as well.

[ronjeremy_69]

peterlaursen wrote on Aug 13 2008, 12:16 PM:

There is a setting in 'preferences' like 'open tables as default'.

awesome!

peterlaursen wrote on Aug 13 2008, 12:16 PM:

We are cautious to save the grid/text setting/preference. It could confuse users who enable 'text' by mistake. Anyway we will discuss this.

sounds good, thanks.

[ronjeremy_69]

peterlaursen wrote on Aug 12 2008, 09:58 AM:

We have now started the release process for 7.1 beta1.

Release notes tell (among others):

In 10-15 minutes you should be able to download it!

oh…my… THIS IS SO AWESOME! THANK YOU THANK YOU!!!

I just can't believe it — for 3 1/2 years I have consistantly lurked this forum waiting for this news. I just tried it, and it works perfectly. It's going to save so much time!

The below would be nice, but at the moment I am so overjoyed the text feature is actually here that I almost don't notice them:

Can it be made so the text preference is saved after SQLYog closes?

I notice after upgrading from my old version that when a plus is clicked to expand a database that it now takes an extra click on “tables” folder to see the tables. 99.99% of the time i (and probably most others) am working with the tables, so can it be made so the tables folder automatically expands?

Again, thanks so much!

[ronjeremy_69]

peterlaursen wrote on Apr 25 2008, 07:15 AM:

First try here with a Logitech mouse did not reproduce the problem.

Can you please tell the exact mouse model and the driver version?

Did you check if there is an updated driver here: http://www.logitech.com/index.cfm/support_…oads/downloads/

I assume you are using a Logitech driver to support additional 'smart' features of the mouse. Anyway the basic features of the mouse may work with the native mouse driver of the OS. Could you try?

the exact model is the MX Revolution. The driver version is the lates version of SetPoint, 4.24.99

the basic features do work, yes. the issue occurs when using the scroll wheel when there are thousands of records in the text results. if you flick the wheel down to scroll, and then stop the wheel, the buffer keeps scrolling down on its own when it shouldn't. if i copy those thousands of text rows and paste them into the query editor (just for the purposes of testing scrolling there in comparison), the query editor does not exhibit such bad behavior, scrolling down is fast and it stops as it should when you stop the wheel.

[ronjeremy_69]

Bruce Leister wrote on Apr 21 2008, 06:52 PM:

I also find it slightly annoying that I have to click on the Database in the Object Browser, and a again on tables to get a list of the tables in the Database.

I agree that there could be situations where it is not desirable to open the Tables tree (to list the tables), so perhaps we could have an option in Preferences to:

Auto-Open Tables tree when database is first selected (expended)

Bruce Leister

agreed

[ronjeremy_69]

peterlaursen wrote on Apr 23 2008, 12:51 PM:

Can you point to somehow to reproduce this? BLOBs or other types of data, # of rows in the result, # of columns … anything? If you have more systems is this reproducable on every system …

It this is a mouse scrollbar (only) issue, does your mouse use a special driver and not the MS/Windows default driver (like a Logitech driver)??

Yes, it is the Logitech driver (MX Revolution), which works perfectly in the Query editor, Objects tab, History tab. Really the only way i can think to reproduce would be to use a logitech mouse, which I daresay a heck of alot of folks do. Perhaps I can do a screen recording video to illustrate. Really though, its a minor annoyance — while it would be nice to have smooth Logitech scrolling, my main reason for suggesting the switch from custom code to Scintilla is so the table data in text feature can be done ASAP, after three years of delays.

[ronjeremy_69]

Hope the MySQL UC went well for you. So, to clarify, is the Scintilla or the “code of your own” which is the holdup for the table results in text feature? If “code of your own” is the issue, why not make the result and table text use scintilla also — it would most likely also fix the scrolling issue.

[ronjeremy_69]

peterlaursen wrote on Apr 14 2008, 09:30 AM:

I told it was a mistake what I wrote first. We use Scintilla in the Editor tab – and for simple text display (in RESULTs/text, OBJECTs etc.) we don't – this is simpe code of our own. We need a full featured code editor for the Query tab (without it we would never be able to support autocomplete etc.)

Is the scroll issue you are reporting an issue with the editor, the GRIDS or the text tabs?

We have no plans to change scintilla with something else. I do not know if Notepad2 is fit (I once had a very old version that did not support unicode – so this version is definitely not). Also want a tool that depends on the Win32 API only (no foundation classes etc.).

Except for that I think I personally should not comment more on those code internals.

My fault, I should have clarified — it's just when scrolling in the Results tab in Text mode that the scrolling issue occurs.

Scrolling in the Query Editor, History tab, and Objects Tab works nicely! So, if those use scintilla, it works great, dont change a thing!!! Scrolling in Data or Results tab in GRID mode is very slow, but constant — it does not know how to to do accelerated scrolling but it does know when to stop.

Unfortunately the mode I use most, Results tab in Text mode, behaves erratically. So, why not use scintilla for Results tab in Text, and also for the new Data tab in Text feature that will be released any day now?

[ronjeremy_69]

peterlaursen wrote on Apr 7 2008, 08:42 AM:

correction: we only use scintilla in the editor. But problem is basically still the same: to dientify the characterlength of a utf8 string (and not the byte length) without destroying performance. I think we have an idea about it now. But it requires some testing.

Have you considered anything else besides scintilla? My understanding is that Scintilla is a code editor, which is way overkill for simple textual display of result or table data. Notepad2 would be perfect: http://www.flos-freeware.ch/notepad2.html

Another major annoyance of the Scintilla editor is that it does not work correctly with mouse wheel acceleration. When I try scrolling with my Logitech MX Revolution, its unbearably slow and it has no idea when to stop scrolling.

[ronjeremy_69]

peterlaursen wrote on Apr 6 2008, 05:07 AM:

Since we started using UTF8 internally in 6.0 we have a problem.

The problem is that currently we have no way to retrieve in length of a string in CHARCTERS, only as BYTES from the Scintilla editor used for text display. Our own GRID code can handle it however. As a consequence the strings

ABCabcn

Àbcàbcn

ÆØÅæøån

ABCabcñ

.. etc. do not align properly in text mode as UTF8 characters can be 1, 2, 3 bytes long

This already affects OBJECTS tab, RESULT tab in text mode ext. This I think we can live with – though I also think we should now focus on it. But in DATA tab we cannot live with it. So this will have to be solved first.

Um… that is the lamest excuse I have ever heard. first of all, i never have any of those weird characters anywhere in my databases, so it is non-applicable. Second of all, how hard can it be to just produce the output exactly as if the mysql command line client produces it. It's JUST TEXT. Give me one good reason the DATA tab cannot live with it if the results tab can? The results tab, by default, uses your GRID code. then with a preference, it switches to text mode. There is no reason the DATA tab should not be able to toggle back and forth in the exact same manner So now what, its it going to take three more years to figure out?

[ronjeremy_69]

peterlaursen wrote on Dec 19 2007, 07:10 AM:

Sorry for the late reply.

For internal workflow reasons we will have to release 6.2 first. After 6.2 release (estimated 3-4 weeks) we will add this with priority.

I see that 6.5 has been released (im guessing this what you meant by 6.2?) after 4 months — So, can we finally add the 'show table data in text' option (and allow this preference to be saved) “with priority”???

[Author]

Posts