[ronjeremy_69]

peterlaursen wrote on Dec 14 2007, 02:52 PM:

BTW: You may click a database in the Object Browser as well.

I can live with that.

But c'mon now Peter, how many more years until there is a 'show table data in text' option? Didnt Ritesh mention he upped the priority on that like 2 years ago? Such a simple core request, that would make life for coders so much easier, yet all these extra fluff features keep being added.

And how hard can it be to fix the existing 'Show Results In Text' preference to be persistant, similar to the options like word wrapping and autocomplete? I launch an instance of SqlYog maybe 15 times per workday, it gets really old to have to remember to click Ctrl+L each time.

[ronjeremy_69]

ronjeremy_69 wrote on Mar 2 2007, 02:39 PM:

I remain hopeful, so every six months or so I like post a reminder 🙂

It's about that time again — yes, yet another 6 months has gone by. Still remaining hopeful that this quite simple feature, which was promised years ago, will happen soon.

[ronjeremy_69]

Rohit wrote on Jun 17 2007, 11:07 PM:

@ronjeremy_69

I tried the following workaround and it worked great for me!

1. Enable “Show results in Text”

2. Select the table and press Ctrl+Shift+S

3. Press F5

This was quite fast for me!

Am I missing something?

Ctrl+Shift+S/F5 is an unacceptable alternative for a variety of reasons:

A.) The biggest reason, it requires me to not just click the table, but also make two additional keystrokes. Additional keystrokes = wasted time and less productivity, especially when this is something I need to do hundreds (or even thousands) of times per week.

B.) It clutters up the Query pane with a bunch of SQL statements I dont want, so i have to waste time deleteing them.

C.) In the normal case my cusror is not at the bottom of the Query editing pane, the “SELECT …” statement is inserted in the middle or between existing statements, so pressing F5 results in “You have an error in your SQL syntax;”.

D.) The table data needs to appear in the DATA tab, not the RESULTS tab as would occur with F5.

[ronjeremy_69]

Rohit wrote on Jun 14 2007, 10:27 AM:

@ronjeremy_69

You persistence is amazing!

I will speak to the SQLyog team to find out the effort required.

Thanks man. Sometimes I think they won't make the “Show Table Data In Text” option just so I'll continue to frequent the forum and give detailed bug reports 🙂

But seriously, I would have literally saved at least 3-4 days of development time over the last two years if this feature was available. If you're a developer/coder, which I'm sure most of the folks using SQLyog are, it's all about the text. Sure, the grid is nice if I want to change a cell value manually instead of my application doing it, but most of the time I am just wanting to browse the the database results produced by the application I am developing, and selectively highlight/copy some text as input for more testing or building another query. Very often I need to copy-n-paste the column names from the textual results tab into my application source, and to do that currently every time i have to “select * from …blah” (and possibly worry about a limit if the table is large), whereas it would be so nice to be able to just click on a table and have its results displayed in text, adhering to the SQLyog row limit configuration. I realize I can get a table definition in text by clicking the “Objects” tab but it's just not as efficient as having them displayed horizontally along with the table data.

One click. Table data displayed as text instead of in grid. Thats all I'm asking for here.

[ronjeremy_69]

peterlaursen wrote on Jun 14 2007, 08:50 AM:

Now I also tried this.

We will need to consider a columns selection.  it is not very easy to do a 'square' selection in text-mode in RESULT tab.  

Basically we like the idea.  

But we will need to finish what we have started before giving priority to this r

quest and considering possible implementations. 

Cool. Since the mysql text results are fixed-width, being able to select a 'square' is the perfect way to extract some desired text (especially for a web developer who is constantly copying and pasting!)

[ronjeremy_69]

peterlaursen wrote on Jun 1 2007, 08:02 AM:

sorry .. I meant COLUMNS, not ROWS.

I will try this with PSpad!

Peter, were you able to try out Column Selection mode? It would be soooooo nice to be able to use this type of text selection in the results tab!

[ronjeremy_69]

peterlaursen wrote on Jun 1 2007, 03:03 AM:

Yes, 'copy row(s) to clipboard' is a nice idea.  I cannot tell how difficult it would be to implement that.  We will discuss.

This feature has to do with the manner in which you can highlight text you would like to copy. Copying row(s) is the exact opposite of what is being suggested. The current way the Result tab allows you to highlight text IS ALREADY row(s).

For example, first in SQLyog click “Edit” and make sure “Show Results In Text” is checked. Then execute a query of your choosing so that several rows appear in the Result tab. Then somewhere in the Result tab click and hold down your mouse button and start dragging down. See how each ENTIRE row gets highlighted as you drag down?

This requested feature would allow you to drag WITHOUT entire row(s) being highlighted. Peter, since it sounds like you have PSPad, to see what I am talking about in PSPad choose “Edit–>Selection Type–>Column Selection”. Then load a text file or paste a bunch of text into PSPad. Now click somewhere on that text and hold down your mouse button and start dragging. See how you can selectively highlight just a column of text (however wide and long you want) instead of the entire rows being highlighted?

[ronjeremy_69]

peterlaursen wrote on May 4 2007, 01:52 AM:

It is reproduced now.

It is a bug in early MySQL 4.1.x that was fixed in more rounds but only fixed ultimately in 4.1.12!  You can see details in the server changelogs.

We also know a workaround for this, but we do not like it, because it is very dirty and unhealthy SQL we will need to send!  We also need to be perfectly sure that that are no unwanted side-effedcts (for ALL locales and non-western users is the problem!).

We will need a few days for considering this, but anyway next 6.0 release will be in about 1 week only, so we have the time to think about it!

It is working with MySQL 4.1.10 (as shipped with RHEL4 and Fedora3).

Sounds good, though im pretty indifferent if it gets fixed or not, since I can just use 5.29. The new graphic query builder in 6.0 is somewhat neat, but nothing to be excited about. Honestly, Id rather just spend a day of my time testing and migrating to 4.1.10, ignore the collation bug, and for you guys to spend that time instead on “Show Table Data In Text”. And id pay you $100 just out of sheer joy and gratitude.

[ronjeremy_69]

peterlaursen wrote on May 3 2007, 09:02 AM:

we installed a 4.1.7 mySQL server on Windows.  the issue that you report is not reproducable.

Please explain very much in detail as I requested before!

sorry, i had to reinstall it to play. i can connect just fine, and while i previously thought no queries were running at all, its just when i have a 'where' clause in a query.

here is the complete history which reproduces the issue for me:

/*[5:17:20 PM][ 0 ms]*/ Set names 'utf8'

/*[5:17:20 PM][ 0 ms]*/ show databases

/*[5:17:23 PM][ 0 ms]*/ use `test`

/*[5:17:26 PM][ 16 ms]*/ CREATE TABLE `requests` (`id` int(1) NOT NULL auto_increment,`sitename` varchar(200) default NULL,PRIMARY KEY (`id`)) ENGINE=MyISAM

/*[5:17:27 PM][ 0 ms]*/ select * from requests where sitename = 'www.blah.com'

the last query produces: “Error Code : 1267

Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='”

note that if i just do “select * from requests” the error does not appear.

i tried the above on a second machine which is also running 4.1.7

If you cannot reproduce with the above, Peter please pm me and ill see if i can setup a guest login for you.

[ronjeremy_69]

peterlaursen wrote on May 2 2007, 03:06 PM:

I now notice this

4.1.7 was the first version in the 4.1.x tree that had the 'stable' predicate.  But the charset concept and unicode implementations were new.  And still very buggy.

I will have to say that we cannot support server versions antique as this one!

What OS is this server running?  There is a lot of red hat's running 4.1.10 in the world (the one that it shipped with originally).  But 4.1.7 is a rare version! (and the before mentioned red hat's should have 4.1.20 installed.  Official RH RPMs are available at least for 4.1.20.  We did this on this server itself about 9 months ago and that solved several issues!

Its running redhat 8, and both the application and server are production and considered stable so i dare not mess with it.

I guess ill just have to stay with the current stable version of SqlYog that works as it always did. Not a big deal, unless you were to finally come out with the “Show Table Data In Text” feature for which I have been waiting 2 years. Then, I'd consider going to the trouble of upgrading from 4.1.7 to 4.1.20 🙂

[ronjeremy_69]

peterlaursen wrote on Apr 30 2007, 06:20 AM:

Please execute

SHOW VARIABLES LIKE '%character%'

on both the remote and the local 5.0 server

remote:

Variable_name Value

---

---

character_set_client latin1

character_set_connection latin1

character_set_database latin1

character_set_results latin1

character_set_server latin1

character_set_system utf8

character_sets_dir /usr/share/mysql/charsets/

local (5.0):

Variable_name Value

---

---

character_set_client latin1

character_set_connection latin1

character_set_database latin1

character_set_filesystem binary

character_set_results latin1

character_set_server latin1

character_set_system utf8

character_sets_dir /usr/share/mysql/charsets/

peterlaursen wrote on Apr 30 2007, 06:20 AM:

Can you paste the complete HISTORY in here. It will tell us what succeds and what does not!

no query succeds at all.

[ronjeremy_69]

this was fixed a couple months ago — what version are you currently using?

[ronjeremy_69]

Thank you, Peter. After downgrading to 5.22 things returned to normal. In 5.23, the increased CPU usage was noticable when pretty much typing anything into the query editor (a slight lag in a character appearing in the editor after being typed). If i tried just typing many characters really fast, the CPU usage shown in task manager would be unusually high.

[ronjeremy_69]

This has happened to me also on occasion, maybe once a month or two so its not too big of a deal. Rebooting the computer always fixes it.

[ronjeremy_69]

This wasnt exactly like the old bug, but was close, and is fixed with the latest release.

See this post from last week:

http://www.webyog.com/forums/index.php?showtopic=2760

[Author]

Posts