Why does wappler not like datetime in external created databases - Wappler rerwriting the MYSQL Mode?

#22

Actually that is not true. The commands you used are for setting the sql mode temporary and are reset when the MySQL server get restarted, not by Wappler. But as I said earlier you shouldn’t need to change the sql mode at all.

I know it is difficult to track down the issues you have and it takes some time but somehow you pick the most difficult route to reproduce and solve them and stumble to many other issues a long the way. This makes it also very difficult for us to track down tge original issue.

Usually just a clear single problem report with steps to reproduce is more than enough. And it will cost you less time.

#23

Please change your insert record value to:

and let us know if this fixes your issue.

#24

This actually did fix my issue. I got this same error with this setup:

  • managed database on DigitalOceans
  • datetime column created with nocodb"

Using Wappler to insert date formatted like this throws error

2022-01-01T00:00:00.000Z

After using .formatDate(‘yyyy-MM-dd HH:mm:ss’) the output is:

2022-01-01 01:00:00

And no errors are thrown.

I don’t understand why, because the format with the ‘T’ and ‘Z’ looks correct to me!

Any ideas as to why this would throw an error?