We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If a structure change is made which causes an error, the error is never shown and PHPMyAdmin returns to the structure view as if it has worked.
Steps to reproduce the behaviour:
CREATE TABLE `1_test` ( `id` varchar(10) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB; INSERT INTO `1_test` SELECT 'abc';
id
Length/Values
Error should be shown
#17016 sounds similar, but in this case I am not ticking the checkbox "Online Transaction".
Running the query produced by "Preview SQL" manaually shows the expected error:
The text was updated successfully, but these errors were encountered:
Hi @ChrisHSandN I can confirm that using PerconaDb 5.7 #1265 - Data truncated for column 'id' at row 1 should be displayed
#1265 - Data truncated for column 'id' at row 1
Sorry, something went wrong.
Add ChangeLog entries for #17016 and #17037
7ef1c5f
Signed-off-by: William Desportes <williamdes@wdes.fr>
a8d9f44
williamdes
No branches or pull requests
Describe the bug
If a structure change is made which causes an error, the error is never shown and PHPMyAdmin returns to the structure view as if it has worked.
To Reproduce
Steps to reproduce the behaviour:
idLength/Valuesto 1 (e.g. too small to contain 'abc')Expected behaviour
Error should be shown
Screenshots
Server configuration
Client configuration
Additional context
#17016 sounds similar, but in this case I am not ticking the checkbox "Online Transaction".
Running the query produced by "Preview SQL" manaually shows the expected error:
The text was updated successfully, but these errors were encountered: