On Thu, Jul 10, 2014 at 3:05 AM, Chirayu Chiripal < chirayu.chiripal@gmail.com> wrote:
On Wed, Jul 9, 2014 at 10:58 PM, Isaac Bennetch bennetch@gmail.com wrote:
On 7/9/14, 1:22 PM, Marc Delisle wrote:
Le 2014-07-09 11:34, Isaac Bennetch a écrit :
Hello,
In the course of my testing the new input transformation feature, I've encountered some trouble that Chirayu is unable to reproduce. We've had a bit of discussion privately about it, but wanted to move discussion back to the mailing list.
Note that running his branch[1] will change your pma__column_info table structure; so you may wish to back it up for testing purposes.
The problem at the moment is the automatic table upgrade feature. What is supposed to happen is that, when logging in, PMA_checkRelationsParam() verifies that the correct table structure exists for pma__column_info. If it doesn't, it attempts to run ./examples/upgrade_column_info_4_3_0+.sql (after substituting the correct database and table names if needed). This is all quite good.
On my Debian wheezy 64-bit machine (7.5), the auto upgrade went fine. Do you have a control user explicitely defined?
Thanks for checking. Yes, I do. I'm also on Wheezy, but 32-bit. I'll have to do some further testing, perhaps tomorrow.
I have pushed few commits to fix this issue. Let me know if it works or not.