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

Unable to handle mysql column with INVISIBLE attribute #2802

Open
dcaputo-harmoni opened this issue May 22, 2024 · 2 comments · May be fixed by #3140
Open

Unable to handle mysql column with INVISIBLE attribute #2802

dcaputo-harmoni opened this issue May 22, 2024 · 2 comments · May be fixed by #3140
Assignees

Comments

@dcaputo-harmoni
Copy link

If you create a column with the "INVISIBLE" attribute, atlas throws the following error when inspecting the schema:

Error: mysql: unknown extra column attribute "auto_increment INVISIBLE"

There appears to be no way around this, atlas simply crashes. In my case, I ran into it by accident, because mysql 8 was automatically creating invisible columns by way of the sql_generate_invisible_primary_key setting being enabled (Azure enables this by default for mysql 8 flexible server instances).

@a8m a8m self-assigned this May 22, 2024
@a8m
Copy link
Member

a8m commented May 22, 2024

Thanks for reporting this, @dcaputo-harmoni. We'll look into it, and might add it to the next release.

@JoffreyPlouvier
Copy link

Hi there,

any news about mysql invisible column support?

I get this error when running a migrate diff command on a database with invisible columns

Error: mysql: unknown extra column attribute "DEFAULT_GENERATED INVISIBLE"
mysql: unknown extra column attribute "DEFAULT_GENERATED INVISIBLE"

@yoavweber yoavweber linked a pull request Sep 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants