The last part just meant to say: if you have already defined a constraint and edit the table with adminer, the constraint is not preserved. This is the major bug.
Editing the constraint would be nice, but is not as essential, as to prevent a given constraint.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried every combination of rename the table, rename a column, add a column, remove a column, alter a foreign key, alter a foreign key's target, and I couldn't get it to accidentally drop my check constraint.
Perhaps your MySQL/MariaDB server is an old version or something?
I didn't perfectly understand the last part of your sentence, but I want support for check constraints too, so I made this: https://github.com/vrana/adminer/pull/458, https://github.com/jkoop/adminer/releases/tag/v4.8.2-dev-mysql-check-constraints-1
The last part just meant to say: if you have already defined a constraint and edit the table with adminer, the constraint is not preserved. This is the major bug.
Editing the constraint would be nice, but is not as essential, as to prevent a given constraint.
I tried every combination of rename the table, rename a column, add a column, remove a column, alter a foreign key, alter a foreign key's target, and I couldn't get it to accidentally drop my check constraint.
Perhaps your MySQL/MariaDB server is an old version or something?
I'm sorry. You're right. Maybe I mixed sth. up.
At least it would be nice, to see on table page, that a constraint is defined on that table. IÄm not sure, if you added this with your commit.
Yeah, I did that.
Great! Thanks you!
Fixed by 550289de.