MariaDB 10.2.4 and later TIMESTAMP

Wappler General Bugs
#1

======== TEMPLATE BUG FORM ========

Wappler Version : 2.2.2
Operating System : MAC/PHP

Expected behavior

What do you think should happen?

Using MariaDB version 10.2.4 and later (I am now using 10.3.17) a TIMESTAMP should be updated using a server connect update action. Previous versions of mariadb (10.0.38) did not have this issue.

Actual behavior

What actually happens?

Error 500.

How to reproduce

  • Detail a step by step guide to reproduce the issue
  • A screenshot or short video indicating the problem
  • A copy of your code would help. Include: JS, HTML.
  • Test your steps on a clean page to see if you still have an issue

Using a MariaDB version 10.2.4 and later, create a timestamp column and attempt to update that column using a server connect update action. After receiving the 500 error, modify the config of the mariadb server with the following:

[mysqld]
sql_mode = NO_ENGINE_SUBSTITUTION,NO_AUTO_CREATE_USER

Execute the server update again, and it will succeed.

Reference:
MariaDB 10.2.7 doesn’t accept trailing Z for DATETIME timezone when inserting, but earlier version does

SQL Update
Is Not Null doesn't work on timestamp field
#2
#3

Is this still an issue? Maybe @patrick should review it again

#4

Not sure…once I found the mysqld setting, I moved on and nothing has pulled me back.

#5
#6

This has already been fixed

#7