Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Table View Ui And Features Sucks #30274
    DanielD
    Member

    1, true still requires mousing over tiny icon instead of filter being immediately visible without action needed.

    2, you should, it's common thing to require more than one condition

    3, yes multicolumn with immediately accessible fields for filtering would solve it

    4, reason why not it is not good enough. why not open new tab with name “Filter Query” is soon as filter is run….

    Regards

    'Aparna' wrote:

    Hi,

    Thanks for your suggestions.

    1. you don't know what was the criteria applied

    In both table data and the result tab once the filter has been applied the filter icon gets enabled and if you put the mouse pointer on the filter icon then the tool tip shows the filter condition that was applied. Please see the attached screen shots.

    2. only one filter at the time can be applied

    Yes, at the moment filter is possible only on a single column. This enhancement might be taken into account in future.

    3. To amend the filter you have to go to history copy query and amend or create new filter

    Yes, currently this is the only way to make changes to a query and this will also be solved if multi column filter is considered. Please correct me if i am wrong.

    4.query should be display in the query window so it can be tweaked if needed.

    This cannot be implemented. It gives a wrong impression to the user that the query was executed by him/her and that the query was not a result of the filter action that the user performed.

    in reply to: Table View Ui And Features Sucks #30272
    DanielD
    Member

    Tiny bit of improvement, but still very user unfriendly…

    1, you don't know what was the criteria applied

    2, only one filter at the time can be applied

    3, to amend the filter you have to go to history copy query and amend or create new filter

    4, query should be display in the query window so it can be tweaked if needed

    I just do not get why would you not have this field to type filter criteria right below column name. Tons of grids on the web do it example http://www.trirand.net/demophp.aspx > “Searching/Filtering” > “Search toolbar” such easy improvement.

    Regards

    Daniel

    p.s. Seems like Laurence Jones was right this will never happen.

    'Khushboo' wrote:

    Hi,

    We have released SQLyog 8.6 version with this feature,

    “Custom Filter” in Result/Table Data Tab.

    Please refer to:

    http://www.webyog.com/blog/2010/08/24/sqlyog-%E2%80%93-mysql-gui-8-6-ga-new-features-improved-performance-and-stability/

    Thanks & Regards,

    Khushboo

    in reply to: Table View Ui And Features Sucks #30267
    DanielD
    Member
    'Khushboo' wrote on '13:

    Hi Daniel,

    Thanks for the suggestion.

    The requested feature is already under consideration.

    code.google.com/p/sqlyog/issues/detail?id=727

    We will definitely improve the filter options.

    We will discuss about this feature implementation with other team members and update.

    Thank you.

    Regards,

    Khushboo

    Are you getting somewhere with this?

    in reply to: Table View Ui And Features Sucks #30265
    DanielD
    Member
    'Rohit' wrote on '04:

    We will reply soon. The main problem is not writing the code to apply the filter – but finding a place to accept the filter condition without making the UI clunkier.

    Any suggestions?

    Right below the column name have text field you can type in. In preferences you could set if you want to search as you type of wait for enter. Search query afterwards shown in the query window above so it can be amended as needed if you wanted different type of filter then LIKE '%%' for text or = for numeric fields. Nothing clunky about it! Super fast way of filtering.

    in reply to: Table View Ui And Features Sucks #30259
    DanielD
    Member

    Hi, Thanks for response

    1, good to hear as long as it improvement over current implementation I'm all for it

    2, yes you can, but it's very handy to be able to amend query in the top window immediately

    3, I can write query, point was about making it easier

    4, that is good

    5, that is good

    6, disagree here. you have tables with lot of rows and for example clicking show all rows would be bad idea. Button that you could click to get count of rows within table view would solve the issue of performance if user wants it he could get the info without need to write query.

    7, reference to phpmyadmin was to just to point out where I seen such a thing I was not comparing products. This one is nice to have but can live without.

    Few more things:

    8, do you plan to support searching on whole DB? result would then show in what tables searched term was found?

    9, do you plan to have insert/edit form? would open new windows with fields listed vertically

    Regards

    'peterlaursen' wrote on '28:

    Nothing new here. I do not agree that this is 'basic features'. Refererence to phpMyAdmin is irrelevant for us. phpMyAdmin is not a standard – it is just one program among many. And very slow to work with.

    We do plan to add more filtering options as requested over time – but it only requires the most elementary knowledge of SQL/SELECT syntax to have results in the RESULT tab as requested. 

    1) we have chosen another implementation.

    2) You can filter again??

    3) write a SELECT query with a WHERE/HAVING clause. But this is planned (with low priority).

    4) taken ad notam.  Good point.

    5) planned for near future

    6) Because with some table engines (like InnoD:cool: retrieving a rowcount is either very slow (up to several minutes with a large table) or inaccurate.  We do not design for MyISAM – we design for MySQL – and all engines supported with MySQL. Execute SELECT COUNT(*) or see the information in INFO tab (using SHOW TABLE STATUS).

    7) No plans to support this.  There are various problems with Primary/Unique/Foreign keys with a reasonable indexed table. I believe such feature in mostly useful for people not designing proper schemas and tables or who have very simple tables only. We do however have requests for 'duplicate row' (what is not scheduled and no guarantee that we will ever do it).

    We will discuss point 4 after New Year.  The rest of the points do not change our plans.

Viewing 5 posts - 1 through 5 (of 5 total)