Recent changes to 4856: Error with PMA_DisplayResults->getTable()

#4856 Error with PMA_DisplayResults->getTable()

2015-04-21T06:11:30.285000Z

assigned_to: Madhura Jayaratne --> nobody

#4856 Error with PMA_DisplayResults->getTable()

2015-04-20T10:28:00.971000Z

I also do not see update time for InnoDB tables in my local machine. However creation time is updated every time I add a column. That is why creation time has been used to invalidates the uiprefs.

#4856 Error with PMA_DisplayResults->getTable()

2015-04-17T20:17:40.239000Z

I also have no update times when either checking information_schema.tables table or running show table status.

#4856 Error with PMA_DisplayResults->getTable()

2015-04-17T20:08:26.137000Z

These are InnoDB tables. I added those lines to the config and see the new column showing last updated date, but none display anything. Even after I subsequently modify a table, the update date isn't showing.

The creation date does show and it's accurate.

#4856 Error with PMA_DisplayResults->getTable()

2015-04-17T12:42:05.616000Z

Thanks.
uiprefs is not suppose to change but the actual table create time should (even though it sounds weird). It is the difference that invalidates the uiprefs and remove the value.

What is the storage engine of this table?

By adding
$cfg['ShowDbStructureCreation'] = true;
$cfg['ShowDbStructureLastUpdate'] = true;
to your config.inc.php you can view the creation and update times of the tables in database structure page. Anything interesting about the values you see for this table?

#4856 Error with PMA_DisplayResults->getTable()

2015-04-17T09:29:10.090000Z

Yes, did exactly as instructed and still got errors. uiprefs didn't change after adding a new column. Is it really supposed to, though? The table create time doesn't change when a column is added.

#4856 Error with PMA_DisplayResults->getTable()

2015-04-17T06:53:28.599000Z

There is an internal mechanism that compares table creation time stored in pmatable_uiprefs and the actual table creation time of the table. When you add a column actual table creation time is updated and col_order in pmatable_uiprefs is discarded if creation time of the table is newer. Of some reason this does not seem to work in you system.

Can you try the following:

Create a new table, add a couple of records
Change column order
Ensure that create_time stored in pma__table_uiprefs and actual creation time (seen in information section of table structure page) is same
Add a new column
See whether error appears and if so check for create_time in both places

#4856 Error with PMA_DisplayResults->getTable()

2015-04-17T06:29:16.517000Z

Ah, yes. Logging out fixed it. So it seems to have been the col_order and col_visib settings for that table.

And I figured out how to reproduce it. Reorder columns in browse (I don't even remember doing this / maybe accidentally), add column in structure, browse, get errors.

#4856 Error with PMA_DisplayResults->getTable()

2015-04-17T05:42:52.072000Z

Old values are probably still in the session. Can you try login out and try again?

#4856 Error with PMA_DisplayResults->getTable()

2015-04-17T05:06:46.619000Z

Thinking that the col_order and col_visib arrays looked suspicious with only 8 columns, I set this field to just []. But the errors persist.