#4409 Not displaying results of archive table

4.2.1
pending
None
1
2014-11-27
2014-05-14
Marc
No

Trying to display results from an archive table causes an internal server error due to maximum execution time:
PHP message: PHP Fatal error: Maximum execution time of 30 seconds exceeded in /usr/share/phpmyadmin/libraries/DisplayResults.class.php on line 197

Showing the results by command line works fine.

Additional information:
Data in table: 1,1 MiB
Entries: 49,291
Line-length 22 B

Discussion

  • Marc
    Marc
    2014-05-14

    using sql to display the results works fine.
    select * from table limit 100
    shows the wanted results. But using the "Display" Tab does not.

     
  • Marc Delisle
    Marc Delisle
    2014-05-26

    Hi,
    which PHP version ?
    Which MySQL version (server and client) ?
    Which extension (mysql, mysqli) ?

     
  • Marc
    Marc
    2014-05-26

    PHP 5.5.12
    mariadb-5.5.37
    mariadb-client-5.5.37
    php-mysqli-5.5.12

    But as stated, there has to be a query which is executed by clicking on "Display" Tab. Since queries on archive engine ALWAYS causes a table scan if not limited, I assume this to be the problem.

     
    • assigned_to: Madhura Jayaratne
     
  • I am unable to reproduce the problem with an archive table having a couple of millions of records. A LIMIT clause is added to the query executed when "Browse" tab is clicked unless "Show all" button has been previously clicked. "Show all" directive is remembered in the session and should not last after the session terminates. Do you still have the issue? When you say "Display" tab, do you mean "Browse" tab?

     
    • status: open --> pending
     
  • Marc
    Marc
    2014-11-27

    sorry, I don't have phpmyadmin 4.2 anymore. There was an update which moved me back to 4.1.14.7

    But still I don't like the new versions, they are so slow. Currently I do many things in mysql command line.
    Showing a customer table takes ~3 minutes in phpmyadmin and 5 seconds in commandline (160 columns, many set, enum-columns). You should really think of the whole bunch of js-code is really needed. E.g. the sorting, inline edit, rearanging of columns (which is quite annoying). Even I don't understand, why the js-code (~3MB) is downloaded twice, once on login-screen, second time after login.