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

Jump to bottom

Can't change AUTO_INCREMENT #11930

Closed
HLeithner opened this issue Feb 9, 2016 · 2 comments
Closed

Can't change AUTO_INCREMENT #11930

HLeithner opened this issue Feb 9, 2016 · 2 comments
Assignees
@nijel
Labels
Bug A problem or regression with an existing feature
Milestone
4.5.5

Comments

@HLeithner
Copy link

I its not possible to set the auto increment value in phpmyadmin 4.5.4.1 on a MyISAM table.

After changing the value in the Operations tab, the page reloads and says SQL query was ok.
But some options are missing in "Table options" box and "Table maintenance" box. also the value has not changed.

Here are some screenshots

before

after
@nijel
Copy link
Contributor

nijel commented Feb 9, 2016

Same happens with InnoDB on QA_4_5, QA_4_6 and master.

@nijel nijel added the Bug A problem or regression with an existing feature label Feb 9, 2016
@007durgesh219
Copy link
Contributor

This is because of the case issue in setGlobalVariablesForEngine in libraries/operations.lib.php:1873. converting $tbl_storage_engine to upper case will fix it.

007durgesh219 added a commit to 007durgesh219/phpmyadmin that referenced this issue Feb 9, 2016
@007durgesh219
Fix Can't change AUTO_INCREMENT, Issue phpmyadmin#11930
224807b 
Signed-off-by: Durgesh <007durgesh219@gmail.com>
@nijel nijel added this to the 4.5.5 milestone Feb 9, 2016
@nijel nijel self-assigned this Feb 9, 2016
nijel added a commit that referenced this issue Feb 9, 2016
@nijel
Correctly document what this function expects
84ed3ae 
Issue #11930, #11931

Signed-off-by: Michal Čihař <michal@cihar.com>
@nijel nijel closed this as completed in afe00d7 Feb 9, 2016
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@nijel nijel

Labels
Bug A problem or regression with an existing feature
Projects
None yet
Milestone
4.5.5
Development

No branches or pull requests
3 participants
@nijel @HLeithner @007durgesh219