Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status -> Processes doesn't show full query #14800

Closed
spacepille opened this issue Dec 20, 2018 · 5 comments
Closed

Status -> Processes doesn't show full query #14800

spacepille opened this issue Dec 20, 2018 · 5 comments
Assignees
Labels
Bug A problem or regression with an existing feature
Milestone

Comments

@spacepille
Copy link

spacepille commented Dec 20, 2018

Describe the bug

A click on the <-T-> on SQL query in Status -> Processes is without function. It doesn't show the full query.

To Reproduce

Steps to reproduce the behavior:

  1. Go to Status -> Processes
  2. Click on <-T-> behind SQL query
  3. And see that nothing happens

Expected behavior

It should show the full SQL query.

Screenshots

grafik

Server configuration

  • Operating system: Ubuntu 14.04.1 LTS
  • Web server: nginx/1.4.6
  • Database version: 10.0.27-MariaDB-1~xenial-wsrep - mariadb.org binary distribution, wsrep_25.16.rc3fc46e
  • PHP version: 5.6.34-1+ubuntu14.04.1+deb.sury.org+1
  • phpMyAdmin version: 4.8.4 (up to date)

Client configuration

  • Browser: Firefox Devloper Edition 65.0b4 (64-Bit)
  • Operating system: Windows 10 Pro
@williamdes
Copy link
Member

williamdes commented Dec 20, 2018

79548c0 is the commit that introduced this issue

Successfully reproduced on demo servers (root, no password)

@williamdes williamdes added the Bug A problem or regression with an existing feature label Dec 20, 2018
@williamdes williamdes added this to the 4.8.4.1 milestone Dec 20, 2018
@ibennetch
Copy link
Member

@williamdes @MauricioFauth Has there been any more progress on fixing this bug?

@williamdes
Copy link
Member

@ibennetch I did not have any time to fix this issue and #14833 is maybe related to this issue ;)

@still-dreaming-1
Copy link

still-dreaming-1 commented Apr 16, 2019

The problem in the stable version is it is using the POST value instead of the GET value. I peeped at the latest code and it seems that may have been fixed. However, I also feel the logic should be fully reversed to use FULL by default rather than after explicitly requesting this. Otherwise it is basically setup to be annoyingly almost useful by default and only actually useful upon request. Or at the very least there should be a configuration option to make FULL the default. Occasionally people send me screenshots of partial long running queries from this page, which is almost helpful.

@williamdes williamdes added this to the 4.8.6 milestone Apr 27, 2019
@williamdes williamdes self-assigned this Apr 27, 2019
williamdes added a commit that referenced this issue Apr 27, 2019
Signed-off-by: William Desportes <williamdes@wdes.fr>
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug A problem or regression with an existing feature
Projects
None yet
Development

No branches or pull requests

5 participants