You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The custom_field_custom_fieldset table is missing the primary key.
This causes problems on MySQL v8, in particular on cloud hosted databases like Digital Ocean which requires the primary key for replication & data integrity.
Please add a primary key to this table to resolve this issue (all other tables appear to be okay).
Thank you,
Reproduction steps
Install SnipeIT
Run a query for tables that are missing the primary key
custom_field_custom_fieldset is missing primary key
...
Expected behavior
The primary key should be added to prevent replication & data integry issues on clustered setups
Screenshots
No response
Snipe-IT Version
v5.4.1 build 6746 (g3e22dce11)
Operating System
SnipeIT Docker Image
Web Server
NGINX
PHP Version
7.3
Operating System
No response
Browser
No response
Version
No response
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Debug mode
Describe the bug
The
custom_field_custom_fieldset
table is missing the primary key.This causes problems on MySQL v8, in particular on cloud hosted databases like Digital Ocean which requires the primary key for replication & data integrity.
Please add a primary key to this table to resolve this issue (all other tables appear to be okay).
Thank you,
Reproduction steps
...
Expected behavior
The primary key should be added to prevent replication & data integry issues on clustered setups
Screenshots
No response
Snipe-IT Version
v5.4.1 build 6746 (g3e22dce11)
Operating System
SnipeIT Docker Image
Web Server
NGINX
PHP Version
7.3
Operating System
No response
Browser
No response
Version
No response
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: