You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nunoperalta opened this issue
Feb 4, 2022
· 2 comments
Assignees
Labels
BugA problem or regression with an existing featurehas-prAn issue that has a pull request pending that may fix this issue. The pull request may be incompleteuiIssues relating to the user interface
In the New Table page,
The VIRTUAL attribute is lost when we add new column (pressing "Go").
The Expression isn't lost, so if we put the "VIRTUAL" attribute again, the Expression field appears just below, with the saved expression.
The problem is that if you don't notice this after adding a new column,
that column will not be VIRTUAL when you Save/Create the new table.
To Reproduce
Steps to reproduce the behavior:
On a database, press "New"
Add a primary key
Add a "test" field
Select "VIRTUAL" on that "test" field, and add some expression
At the top, press "Go" to add 1 column
"VIRTUAL" is lost in the "test" field.
Press "Save" at the bottom
Expected behavior
"test" field should be VIRTUAL GENERATED
Screenshots
"test" didn't save its VIRTUAL GENERATED attribute
Server configuration
Operating system: Docker
Web server: Docker
Database version: MariaDB 10.5
PHP version: Docker
phpMyAdmin version: 5.1.2
Client configuration
Browser: Google Chrome
Operating system: Windows 10
Additional context
The text was updated successfully, but these errors were encountered:
williamdes
added
Bug
A problem or regression with an existing feature
ui
Issues relating to the user interface
labels
Feb 6, 2022
williamdes
added
affects/6.0
This issue or pull-request affects 6.0.x releases (and maybe further versions)
confirmed/5.2
This issue is confirmed to be reproduced on 5.2 at the time this label was set
confirmed/6.0
This issue is confirmed to be reproduced on 6.0 at the time this label was set
labels
Oct 26, 2022
williamdes
added
has-pr
An issue that has a pull request pending that may fix this issue. The pull request may be incomplete
and removed
affects/5.2
This issue or pull-request affects 5.2.x releases (and maybe further versions)
affects/6.0
This issue or pull-request affects 6.0.x releases (and maybe further versions)
confirmed/5.2
This issue is confirmed to be reproduced on 5.2 at the time this label was set
confirmed/6.0
This issue is confirmed to be reproduced on 6.0 at the time this label was set
labels
Nov 20, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
BugA problem or regression with an existing featurehas-prAn issue that has a pull request pending that may fix this issue. The pull request may be incompleteuiIssues relating to the user interface
Describe the bug
In the New Table page,
The VIRTUAL attribute is lost when we add new column (pressing "Go").
The Expression isn't lost, so if we put the "VIRTUAL" attribute again, the Expression field appears just below, with the saved expression.
The problem is that if you don't notice this after adding a new column,
that column will not be VIRTUAL when you Save/Create the new table.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
"test" field should be VIRTUAL GENERATED
Screenshots
"test" didn't save its VIRTUAL GENERATED attribute
Server configuration
Client configuration
Additional context
The text was updated successfully, but these errors were encountered: