[peterlaursen]

If I am not mistaken we had a similar report many years ago and concluded that this was a limitation with Wine. But things have developed in the meantime, and we should check again.

[peterlaursen]

It looks like a proxy/caching issue to me.

 

Can you please try to rename the tunneler file? No specific name is required (only the file extension must be .php or another extension that the PHP installation recognizes).

[peterlaursen]

I have added this to our issuetracker here:

https://code.google.com/p/sqlyog/issues/detail?id=2046

[peterlaursen]

+ I think that if you use the “AS” keyword before the alias it will work?

[peterlaursen]

The reason why I advise to quote as an `identifier` and not as a ‘string’ is because of this:

http://bugs.mysql.com/bug.php?id=72774 (What I think is a bug in MySQL).

 

If I am right that this is a server bug, I think the best advice is to avoid having alias’es starting with a number.

[peterlaursen]

You can quote the alias’es. According to MySQL documententation alias’es may be quoted as either a string or an identifier. Please try to `backquote` the aliases for instance.

 

But it is a verified bug with our formatter as this “SELECT ‘aa’ AS 1aa;” is a valid statement (I think from MySQL 5.1 at least).

[peterlaursen]

Am I right in understanding it like this 

 

“request that the RESULT tab of every QUERY tab (if populated) should memorize the last focus so that after swithcing to another QUERY tab and back the same cell would have same focus as before”.

 

We would then have to consider GRID, FORM and TEXT modes independently.

[peterlaursen]

@flyingrcarlson .. I think your original question here was something else than what we understood and another user continued in the thread. 

 

After reading your original post I am not quite sure if your question was about “Galera Cluster” or “NDB cluster”. Did you have your question(s) answered?

[peterlaursen]

Please consider this query:

SELECT 

  COUNT(*) AS '#rows',

  COUNT(`columnname`) AS '#rows NOT NULL',

  COUNT(DISTINCT `columnname`) AS '#DISTINCT rows' 

FROM `tablename`;

 

Isn’t this basically what you are looking for (without the need to type any tablename or columnname yourself)?

[peterlaursen]

Actually there could be a single option (‘column statistics’) returning

 

1) total rows

2) NULL rows

3) NOT NULL rows

4) DISTINCT rows

 

.. for the column. Maybe for indexes we could then add a option for “index cardinality” in the context menu.

[peterlaursen]

Thanks for your interest in SQLyog.

 

I will not comment on your experiences with Workbench. Over the 10+ years we have co-existed with GUI tools from MySQL/Sun/Oracle as well as from others, we have avoided ‘mud-throwing’ at each others.  And we are not the ones who will be changing that.

 

It is also very unlikely that we will do any changes to the INFO tab as proposed. This is mainly for perfomance reasons.  Currently INFO tab is populated by fast running SHOW queries (see yourself in the HISTORY tab after selecting the INFO tab what the queries are).  What you propose could cause the INFO tab to populate very slowly with large data. All depending on what indexes exist and the storage engine used it could take several minutes (and ‘several’ could be ’20’ or more).

 

What remains is then proposals for the Object Browser.  If I understand you propose more content in the context menu of a column object here.  This context menu could have entries added like

* NOT NULL count

* NULL count

* DISTINCT count

* (more?) 

.. what would then paste a query to the editor that would discover the selected option.

 

 

Please confirm that I understood and if I overlooked something. 

[peterlaursen]

And one more thing you should be aware of is that when dumping and importing a dumps with VIEWs, is that first a temporary table will be created for each VIEW, next the VIEW is created and finally the table is dropped.  This is necessary to handle ‘VIEWS built on VIEWS’ as there is no way to guarantee in what order VIEWS are dumped. 

 

 

 

All this is *defacto standards* with all MySQL tools – including the official ‘mysqldump’ utility. And it is at least the 50th time I reply along these lines here (but no problem). 

[peterlaursen]

It means “treat as a commented if server version in less than 5.01. If server version is 5.01 or higher don’t treat as a comment”.

[peterlaursen]

This 

 

/*!50001

 

.. is NOT a comment.  Please read MySQL documentation at http://dev.mysql.com/doc/refman/5.5/en/comments.html.

[peterlaursen]

The links are very old.  We don’t use the Issueburner system anymore.

 

Please send a mail to [email protected] and we will reply there.

[Author]

Posts