[NicholasA]

'peterlaursen' wrote on '06:

BTW: do you know that you can sort data (“ORDER BY”) by clicking on the column header?

A GROUP BY with no aggregate function is rarely usable.  Best of all if you could tell what the SQL should be like.  If we have a TAB populated with “SELECT * FROM TABLE” what should the SQL look like when operating such functionality?

You make a good point. I'm not sure if this is actually useful in helping you build queries, or whether it is just really useful in exploring and summarising your data in real-time. You are right, a true group-by would often have aggregate functions, whether this function actually just groups the actual records.

It is really useful from a data exploration point of view…a little like dragging and dropping fields in pivot tables (though again, this isn't a cross-tab, it's just grouping matching records).

So maybe this is just an interface and data exploration enhancement, rather than query building tool.

[NicholasA]

'peterlaursen' wrote on '06:

The problem is that if one client adds this functionality (client-side) it will cause problems if more clients are allowed to create tables.  For instance if you upgrade a 'standard application' (like this Forums software) the upgrade script may add new tables.  And another client (SQLyog will not know).

Such functionality should be a server-side functionality. Same applies to ROLES in User Management for instance. But MySQL server has no such functionalities.

Peter,

I agree that ideally this should be done server-side in the database, and I understand catalogs are used for this purpose, which MYSQL doesn't support.

However I don't see why the client software couldn't provide such a client-side feature as a great selling point, helping to fill the gap.

I don't see the conflict? The grouping feature would be a personal feature for an admin's use. It would be invisible to anybody else. SQLYog would just provide the ability to allow him to organise his tables in client-side virtual folders. The ordinary tables tree would still be there, this is an optional capability. If somebody else adds another table, it appears in the table list as per usual.

[Author]

Posts