-
Notifications
You must be signed in to change notification settings - Fork 231
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
Error: mysql: parse precision "/*" for MariaDB #2019
Comments
Hey @arroadie 👋 Please see @giautm's answer here: #1985 (comment) You can pre-encode your password and store it this way, or use the env "staging" {
url = "maria://${var.user}:${urlescape(var.password)}@${var.host}/database"
} Closing, but please feel free to reopen or join our Discord community in case you need more help with this. |
The problem is not the password. Atlas can reach other schemas in the same DB. |
Oh, got it. Sorry for the misunderstanding. Can you please write here the MariaDB and Atlas versions are you using? Do you get it also with the latest version of Atlas? |
No problem. I tried to make it clearer and it actually caused more confusion :P Atlas info
MariaDB
|
@arroadie, are you able to detect what table is causing this? If so, can you please paste it here (or send me on Discord its definition - |
I can't. There are 64 tables in this database. Is there a way to increase the verbosity of the process? |
Or if there's a way to tell the process to run on a single table, I can iterate over all programmatically and check which one is at fault... |
I added a small patch to add this info (table and column): #2023. I'll merge it and release binaries, you can test it right after. |
@arroadie, I released new binaries in case you want to check this. Thanks 🙏 |
are those obtained with the same curl > bash process? I updated the same way and had the same results
|
I released yesterday a tagged version (below is the latest canary version). Can you test it again?
|
Is the artifact created or should I build it? |
this version inspected the tables without issues! |
Happy to hear this. Thanks for confirming this. |
Didn't find a way to print debug logs, but this is the configuration I'm using (information replaced to $VAR)
Let me know if there's a way to get more insight on the error
The text was updated successfully, but these errors were encountered: