-
Notifications
You must be signed in to change notification settings - Fork 8
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
TIMESTAMP precision not working on older MySQL versions. #13
Comments
You need to upgrade your MySQL version to >=5.6.4 because the milliseconds precision is not supported previously. This remind me to check the MySQL version on plugin start-up. |
After some tests, I can't add inside the plugin a database engine version checker due to MySQL different engines versions. |
how about:
? |
It works if everyone uses the same standard engine but if, for example, I use MariaDB, the version will change so, I can't compare two engines because they have different version. It's like to compare Firefox version to Chrome. |
By the way I advise you to update your MySQL version and don't change the tables because the plugin logs could not work properly. |
You are right, but both of them are web browsers and do similar things, so it's possible. I've made following function that seems to work:
|
I've did it, but your plugin has insane CPU usage on my server and laptop, so I can't use it. |
There are a lot of engines, not only 2. If someone want to use the plugin must follow the minimum requirements and, said among us, last MySQL version is 8.0 and you're using 5.5 yet🤣 |
Which OS are you using? By the way, the cause is libasynql falsely uses the 100% of CPU (see #12) |
To demonstrate just check the TPS |
Issue description
Steps to reproduce the issue
OS and versions
Plugins
Plugins: AlwaysSpawn v2.2.4, FileManager v1.0.1, DevTools v1.13.5, BedcoreProtect v0.5.2, EconomyAPI v2.0.9, EconomyLand v2.0.9, SimpleAuth v2.1.3
Crashdump, backtrace or other files
I'm getting following non-fatal error:
I'm getting this error for all queries that have
TIMESTAMP(x)
inside.My solution: copy queries, remove
(x)
part and execute them on SQL server. After starting you will still have that errors, but at least plugin will work.The text was updated successfully, but these errors were encountered: