DB Error #1048 after Upgrade to 1.12 from 1.10

SwamReaper91

Hey Folks,

I upgraded my osticket to 1.12. But now it keeps throwing me this error:
DB Error #1048

[INSERT INTO ost_config (id, namespace, key, value, updated) VALUES (NULL, 'core', 'vid', 'ost-1546460168', CURRENT_TIMESTAMP)] Column 'id' cannot be null

---- Ablaufverfolgung ----
#0 (root)/include/mysqli.php(199): osTicket->logDBError('DB Error #1048', '[INSERT INTO os...')
#1 (root)/include/class.addfunctions.php(267): db_query('INSERT INTO ost...')
#2 (root)/include/class.addfunctions.php(234): addFunc::getVid()
#3 (root)/include/staff/system.inc.php(67): addFunc::checkForUpdates()
#4 (root)/scp/system.php(23): require('/home/users/tic...')
#5 {main}

My Server has these specs:
OS: Debian 10.1
Kernel: 4.19.0-6-amd64
Webserver: Apace 2.4.38
PHP: 7.3.9-1
DB: MariaDB 5.5.5-10.3.17

Can somone please help me to get rid of this error?

Thanks in advance
Adrian

SwamReaper91

As a workaround I deactivated the loging, but that can't be the answer 🙂

ntozier

Which version of 1.12 did you upgrade to?
Something is trying to add a line to your ost_config table.
What? no idea. Maybe a plugin?
I have nothing that matches that key in my ost_config on any of my production machines (all running 1.12.2).
Your database software does not like that the SQL: query isn't telling it explicitly what the id is, and is passing a null.
Which when i do that on my installations jumps to the next unused id#.
I would guess that this is either:

your db configuration
there is a difference in how Maria handles this and MySQL handles this, and its coded for MySQL.

Since the query works for me I did some digging and found this in the MariaDB documentation:

Inserting
If a NULL value is single-row inserted into a column declared as NOT NULL, an error will be returned. 
However, if the SQL mode is not strict (default until MariaDB 10.2.3), if a NULL value is multi-row 
inserted into a column declared as NOT NULL, the implicit default for the column type will be inserted 
(and NOT the default value in the table definition). The implicit defaults are an empty string for string 
types, and the zero value for numeric, date and time types.

Since MariaDB 10.2.4, by default both cases will result in an error.

Looks like you have SQL mode set to STRICT.