incrediblePBX2020 / raspi 4
Avantfax GUI not working properly, having to backpage on login, wouldn't update fields, etc.
I could live with that, but fax to email was failing too. SQL command invoked by a Avantfax function
would fail and error out of db query before completing with "Incorrect integer value: '' for column", etc.
The issue seems to be that somewhere along the way the databases updated versions for mysql/mariadb started
enforcing tighter tolerances on updating data and matching column types. Like updating a Integer column with and empty field " "
will fail. It seems Avantfax needed to update their code to follow and have not.
Fix;
The issue is to turn off strict mode.
login into mariadb and....
mysql -u root -p passw0rd
MariaDB [(none)]> SELECT @@GLOBAL.sql_mode;
+-------------------------------------------------------------------------------------------+
| @@GLOBAL.sql_mode |
+-------------------------------------------------------------------------------------------+
| STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION |
+-------------------------------------------------------------------------------------------+
MariaDB [(none)]> SET GLOBAL sql_mode = 'NO_ENGINE_SUBSTITUTION';
Query OK, 0 rows affected (0.000 sec)
MariaDB [(none)]> SELECT @@GLOBAL.sql_mode;
+------------------------+
| @@GLOBAL.sql_mode |
+------------------------+
| NO_ENGINE_SUBSTITUTION |
+------------------------+
1 row in set (0.001 sec)
To permanently set sql_mode;
change etc/mysql/my.cnf
[mysqld]
sql_mode=NO_ENGINE_SUBSTITUTION
restart db and and check.
login into Advantfax GIU and will now work properly. No more "back page" on logging in. actually asked to
change password for first time login instead and now updates and saves info too.
Fixed my errors with fax to email and is working great.
@wardmundy
Avantfax GUI not working properly, having to backpage on login, wouldn't update fields, etc.
I could live with that, but fax to email was failing too. SQL command invoked by a Avantfax function
would fail and error out of db query before completing with "Incorrect integer value: '' for column", etc.
The issue seems to be that somewhere along the way the databases updated versions for mysql/mariadb started
enforcing tighter tolerances on updating data and matching column types. Like updating a Integer column with and empty field " "
will fail. It seems Avantfax needed to update their code to follow and have not.
Fix;
The issue is to turn off strict mode.
login into mariadb and....
mysql -u root -p passw0rd
MariaDB [(none)]> SELECT @@GLOBAL.sql_mode;
+-------------------------------------------------------------------------------------------+
| @@GLOBAL.sql_mode |
+-------------------------------------------------------------------------------------------+
| STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION |
+-------------------------------------------------------------------------------------------+
MariaDB [(none)]> SET GLOBAL sql_mode = 'NO_ENGINE_SUBSTITUTION';
Query OK, 0 rows affected (0.000 sec)
MariaDB [(none)]> SELECT @@GLOBAL.sql_mode;
+------------------------+
| @@GLOBAL.sql_mode |
+------------------------+
| NO_ENGINE_SUBSTITUTION |
+------------------------+
1 row in set (0.001 sec)
To permanently set sql_mode;
change etc/mysql/my.cnf
[mysqld]
sql_mode=NO_ENGINE_SUBSTITUTION
restart db and and check.
login into Advantfax GIU and will now work properly. No more "back page" on logging in. actually asked to
change password for first time login instead and now updates and saves info too.
Fixed my errors with fax to email and is working great.
@wardmundy
Phone System 