Skip to content

Error Encountered When Setting Up MySQL 5.7 Connection #3411

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

Open
ETGit39 opened this issue Mar 26, 2025 · 1 comment
Open

Error Encountered When Setting Up MySQL 5.7 Connection #3411

ETGit39 opened this issue Mar 26, 2025 · 1 comment

Comments

@ETGit39
Copy link

ETGit39 commented Mar 26, 2025

I am encountering an issue while configuring a MySQL connection in Neosync with a MySQL 5.7 database hosted on AWS RDS. The following error occurs during the setup process:​

Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'admin_privileges AS ( SELECT privilege_type FROM INFORMATION_SCHEMA.USER_P' at line 2

The issue is specific to MySQL 5.7. When attempting the same setup with MySQL 8.0.40, also on AWS RDS, the connection is established successfully without any errors.​

Executing the query directly on MySQL 5.7 results in the same error, whereas it executes successfully on MySQL 8.0.

As far as I understand, the error appears to be associated with the use of CTE in the query, which is available only for versions 8 and upwards.

Is there any extra setup we need for making neosync compatible with MySQL 5.7, or are there any suggested work arounds? If not, can we consider adding support for MySQL 5.7?

@nickzelei
Copy link
Member

We build and test Neosync with mysql 8.0. Looks like 5.7 was EOL over 2 years ago.

If that query is failing I am open to updating it if there is an alternative that works for both versions.
That GetRolePermissions function is only used on the test connection page I believe.

Have you tried wiring up a job and seeing if the schema loads or if a job run works? It's possible the other queries will work just fine for you and it's just that one that is broken.

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

No branches or pull requests

2 participants