#4134 (ok 4.1.0-rc1) After deleting all rows on a page, it returns to a blank page

[DisgruntledGoat]

To reproduce:

1. Have a table that spans several pages in Browse mode.
2. Go to the last page.
3. Click "Check all" then delete those rows.

It then goes to a blank table. At the top it says "Your SQL query has been executed successfully" with the delete query below.
Then below that it says "Showing rows 720 - 719 (720 total, Query took 0.0014 sec)"
Then the query box - SELECT * FROM \table` LIMIT 720 , 30` (the table now had 720 rows after deletion).
Then the table headers but no rows of the table.

I would expect it to either go to the previous page (which is now the last page of the table), or maybe the first page. At least it should show some data.

[Abhishek Kandoi]

In my opinion, after deleting the rows, using the Check all, it should go to the previous page. This makes sense according to me.

I am working on it and will probably send a pull request when done.

What do others have to say about this?

[Marc Delisle]

Abhiskek,
I agree with your suggestion.

[Marc Delisle]

Abhishek,
any progress on this?

[Hugues Peccatte]

Hi,

I sent a pull request to fix this bug ( https://github.com/phpmyadmin/phpmyadmin/pull/740 ).

What does the fix?
After deleting row(s) with multi actions submit, I compare the number of rows of the displayed table and the position of the first line to display. If number of rows <= position, position is updated.

I know that this fix added an error in PHPUnit test. I had to include another file in the test class, but in this file and another one, there are 2 functions (that I didn't create) with the same name.
Possibilities:
- Rename one of them;
- Factorize them;
- Don't test (not a good way).

I just didn't want to do a bug fix and update the functions in the same pull request.

Hugues.

[Abhishek Kandoi]

Oh. Sorry Marc that I couldn't reply.
I tried fixing this bug, but got caught up due to my end-term exams.
But I am glad that it is fixed now.