[peterlaursen]

“I then clicked on the single green arrow (execute current query). …!

I think I understand what is happening!

Refreshing Object Browser only has effect on the part of the tree BELOW current selection! to refresh the list of databases the connection itself must be selected. To refresh the list of tables in a database the database must be selected.

In other word: you refresh what is currently selected only! It is made such because if you have lots of very big databases (and/or a slow connection) refreshing everything can take very long time.

Was that the answer that you needed?

[peterlaursen]

I did not see your ticket before replying here!

Please see my comments in the ticket too!

[peterlaursen]

1) “all I see in sja.log is that the job started successfully. The is nothing else.” Is no backup file created/stored?

2) automatic spam filers can be tough to souch autogenerated mails. Did you check all such filters? And are you sure that the 'to-email' is correctly entered?

[peterlaursen]

1) Problem is that this is not supported on the server side (SHOW … ORDER BY). We would then have to implement on the client side

2) This would required that 'show results in text' had effect here too. I think that can be done!

3) Don't know. I will have to ask!

[peterlaursen]

I just added a request to our issue tracker that we display the error log in a 'scrolled down to last line' state.

Please refer to:

http://code.google.com/p/sqlyog/issues/detail?id=310

[peterlaursen]

I am sorry, but I do not fully understand you!

Please try to explain more in detail (step by step) what you do. And from where do you have the dump that you import?

I also think you may be fooled a little by the error message. The error log is cumulative – the latest error message is at the bottom of the log display. The error message that you show here could be a very old eror message! Scroll down to the bottom!

[peterlaursen]

This is a SQLyog issue. Not a MONyog issue. Please post in the correct category! I am moving you …

first reply: you can doubleclick any object in the Object Browser and the name will be inserted in the editor

[peterlaursen]

hehe …

I think I will 'look back' into my mailbox 2 years back and find some Ritesh quotes on Windows versus *nix!

BTW: do you have some decent masala over there ?

🙂 😉 🙂 😉 🙂 😉 🙂 😉 🙂 😉 🙂 😉 🙂 😉 🙂 😉 🙂 😉 🙂 😉 🙂 😉 🙂 😉 🙂 😉 🙂 😉

[peterlaursen]

We will not be able to include this in version 6.05. The reason is that when a column is declared NOT NULL different MySQL versions behave differently with defaults. It was too late we became aware of that, and we will not postpone 6.05 for this reason.

It is still a high-priority 'fix' and it will be added soon!

[peterlaursen]

BTW .. this is Open Source!! I am pretty sure you can handle this! What about a small contribution??

(renaming and reordering query tabs would be nice too!)

[peterlaursen]

Yes, we will add a prompt when the search reahes the end that gives user an option to start again from the beginning.

We will try to add this in 6.06 or 6.1

[peterlaursen]

you are right. we have Alt+n in the data area but nothing similar in the query area.

what would you suggest? ctrl+alt+n ??

[peterlaursen]

The problems with queries to information_schema is that they can be very slow! And it can be a problem with shared hosting as a lot of ISPs have not yet understood, that users may query I_S!

You can read this discussion:

http://www.webyog.com/forums//index.php?sh…ormation_schema

However it is no problem to use different queries with different server versions. One of the first things we do after connection is to SELECT VERSION(). We do a lot of differentiation between 3.23 and 4.0/4.1 and higher allready!

I will not comment more on it tonight!

[peterlaursen]

This is a SQLyog question, not a MONyog question. Please post in the correct category. I will move you … 🙂

It is a basic consideration in the design of SQL-databases that such orders do not matter! However on the client side it is a reasonable idea! The problem is however that SQL syntax does not support it.

For instance: this SQL is used when you expand the columns folder in the Object Browser

Code:

show full fields from `database`.`table`

it would be nice (and supporting your request would be easy) if

Code:

show full fields from `database`.`table` order by `field`

.. worked. but ORDER BY is no supported with SHOW FULL FIELDS . The only way we/SQLyog (as any client) can communicate with the server is using SQL! Sorting on the client side like this is a major request – and I would think that this request should be sent to MySQL (to be implemented in the server) and not to us (to be implemented in a client)! SHOW DATABASES sort – SHOW TABLES and SHOW FULL FIELDs don't. This is a inconsistency in the MySQL Server, I think!

We are very careful NOT to (try to) implement 'server functionalities' in SQLyog.

On the other hand .. ok .. some sorting and/or filtering (even implemented on the client side) could be pretty useful, as long as the server does not.

We will need some time to consider!

[peterlaursen]

yes .. you are correct. SQLyog 6.x encodes such files as UTF8. There is no option not to! if you use the file with a program that does not handle UTF8, there is a problem!

As a workaround you can use version 5.32 for this particular operation. It uses ANSI encoding for such files. This is the only 'short term' solution i can offer.

Download link to 5.32 COMMUNITY:

http://webyog.com/downloads/SQLyog532.exe

[Author]

Posts