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

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Schedule Sql Query Export To Excel File #32818
    Shiro
    Member
    'sathish' wrote:

    Hello Shiro,

    We already have this feature request here in our issue tracker: http://code.google.com/p/sqlyog/issues/detail?id=1696 We will schedule this according to our priority.

    Regards,

    Sathish

    Hi Sathish,

    Thank you for your information 🙂

    Will it be next release?

    in reply to: Feature Request #30075
    Shiro
    Member
    'Shiro' wrote on '02:

    ok, you got the point, when there is no auto_increment as PK. For the last record /first record feature didn't have the weight function usage.

    But as you know most of the time, ppl create table will create an ID as auto_increment as PK.

    If you think this feature is misleading, maybe create as an option, by default it is disable, when ppl like me want to use it got the feature to enable. If this feature really useless or misleading why phpmyadmin and other mysql GUI still keep it? it sure got it purpose. I suggest created as an option.

    so what is the outcome? Will this feature consider on next build?

    in reply to: Feature Request #30074
    Shiro
    Member
    'peterlaursen' wrote on '01:

    Can you please explain me what 'the last record' in a database table is?

    In my understanding there is no order defined for data as they are stored. If you SELECT * from a table (with no ORDER BY) you will not always get data in the same order from the server because

    1) it depends on indexes/keys

    2) after dumping and importing a table rows may be returned in another order than before.

    .. so it can actually be very misleading to claim that some row is the 'last row'. Some users would expect a PK-sort (if a PK exists) – others a timestamp sort (if a timestamp column exists).

    But you are probably right that with an auto_increment INTEGER PK on the table the server will always return rows in same order. But with no auto_increment INTEGER PK, I think such 'feature' is very misleading.

    ok, you got the point, when there is no auto_increment as PK. For the last record /first record feature didn't have the weight function usage.

    But as you know most of the time, ppl create table will create an ID as auto_increment as PK.

    If you think this feature is misleading, maybe create as an option, by default it is disable, when ppl like me want to use it got the feature to enable. If this feature really useless or misleading why phpmyadmin and other mysql GUI still keep it? it sure got it purpose. I suggest created as an option.

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