This issue will be fixed when we release the installer for MOVES3.0.1. However, we have identified a workaround if users need this fix before we release the updated installer. It involves updating MariaDB's configuration:
Find your my.ini file (typically in your MariaDB data folder)
Add the following line somewhere in the [mysqld] section:
sql_mode=STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
Make sure there are no other sql_mode lines in this section (delete them if there are)
Restart the MariaDB service (In the Windows 10 taskbar, search for and open Services, select MariaDB in the list, and click "restart"; if you don't have permissions to do this, restarting your computer will also do the trick).
This issue will be fixed when we release the installer for MOVES3.0.1. However, we have identified a workaround if users need this fix before we release the updated installer. It involves updating MariaDB's configuration:
[mysqld]
section:sql_mode=STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
sql_mode
lines in this section (delete them if there are)