-
Notifications
You must be signed in to change notification settings - Fork 0
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
Schema: browser_session: let the code insert authenticated_at #195
Comments
How is it not portable? For the MariaDB variant, the timestamp creation was taken from Stackoverflow as this snippet properly calculates the UTC unix timestamp with millisecond precision, without daytime-saving derivations. |
Since which MariaDB version does this work? |
5.2 throws as there's no support for precision on the Your MariaDB connection id is 1
Server version: 5.3.12-MariaDB-mariadb122~wheezy (MariaDB - http://mariadb.com/)
Copyright (c) 2000, 2012, Oracle, Monty Program Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> SELECT UNIX_TIMESTAMP()*1000+FLOOR(MICROSECOND(UTC_TIME(3))*0.001);
+-------------------------------------------------------------+
| UNIX_TIMESTAMP()*1000+FLOOR(MICROSECOND(UTC_TIME(3))*0.001) |
+-------------------------------------------------------------+
| 1718031502718 |
+-------------------------------------------------------------+
1 row in set (0.00 sec) |
|
No, as this only saves it with a precision to a second. We use the unix timestamp with millisecond precision on everything related to the However you should keep in mind that MariaDB 5.2 went EOL on the 15/11/2015. |
What I just wanted to express is that even the simpler |
I wasn't aware of the fact that you were talking about MariaDB 10.1 specifically.
But again, 10.1 has been EOL since the 10/17/2020... |
The browser_session.authenticated_at DEFAULT has to go, as it's not portable to MySQL (https://github.com/Icinga/icinga-notifications/pull/203/files#r1624022883).
The text was updated successfully, but these errors were encountered: