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
"Extra" column definition not editable #15994
Comments
|
Hi @Simbiat Thank you for the report, I would say the bug is that it is not selected in the Extra selector automatically when editing the column ? |
|
Did not even notice it was there in the field even :D But, yes, this seems to be the case. Although, I am not sure it's correct to have "on update CURRENT_TIMESTAMP" in the "Attributes" field, because you may need both, say, UNSIGNED and "on update". I am also not sure, whether "CURRENT_TIMESTAMP" is the only possible clause for "on update", although was not able to google anything proving that. |
|
Except the bug do you have comments on the previous message @OlafvdSpek? |
|
As far as I know |
|
is this bug still exists? seems like it's already fixed. as i'm not able to re-produce the bug with the current version. |
|
@iifawzi this is replicable in 5.1.0-rc2, at least. Just follow the steps described in original post. The issue here is that "EXTRA" is not showed by "Edit Column" UI at all (yet, AUTO_INCREMENT is preserved somehow). |
Signed-off-by: William Desportes <williamdes@wdes.fr>

Describe the bug
When editing a column "extra" definitions are not editable and not visible. Only AUTO_INCREMENT is visible and editable as a separate option, but, for example, ON UPDATE CURRENT_TIMESTAMP is not visible or editable. Furthermore, when you try to edit such a column, such extra definition will be lost. It is retained however when exporting the table with such column.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
At least it should show extra definitions and preserve them when changing column through UI. Ideally - also allow to edit them.
Screenshots
N/A
Server configuration
Client configuration
Additional context
N/A
The text was updated successfully, but these errors were encountered: