No longer usable for optimizing tables.

  • Resolved KevinFitz

    (@kevinfitz)


    6 years, 9 months ago

    You used to be able to optimize database tables while ignoring InnoDB tables. Now it wants you to check a box accepting risk. Now you must optimize them along with the rest. So now I no longer optimize any. As often happens with updates, the update is not screened by users but only programmers so fails to please users. Programmers are great. But are not quality control or capable of making a UI without supervision. Programmers think different and need to. Sane companies, notably Apple, never let programmers design interfaces.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author David Anderson

    (@davidanderson)

    Thank you for the issue report. I have filed an issue in our internal tracker.

    (The rest is not accurate, by the way – that’s not how we design our products).

    David

    Thread Starter KevinFitz

    (@kevinfitz)

    Thanks for caring. Unfortunately, you think you are already following user-friendly design protocols. Oh well, not a chance of convincing you otherwise them. Hint: you might start with the language. Few use or understand the specialized language and vocabulary that you throw at us. And it is not from a lack of computer understanding since I can program in several languages. But you can pretend otherwise to keep your happy face.

    Plugin Contributor DNutbourne

    (@dnutbourne)

    Hi,

    The latest release should have resolved the issue with table optimisation. You should now be able to optimise tables normally.

    Thread Starter KevinFitz

    (@kevinfitz)

    Yes, it did fix it. Thanks for your fast work. I have positively reviewed the product in the past and believe it helps to speed up my website. Thanks again.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘No longer usable for optimizing tables.’ is closed to new replies.