Ask, reply and learn. Join the community of Akaunting.
Hi All,
Receiving SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'locale' cannot be null error. had a look at the table (see below) .. is this an issue on SQL 5.7 or do i need to just drop the constraint ?
Thanks in advance..
root@localhost [akaunting]> describe dzo_users;
+-------------------+------------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+-------------------+------------------+------+-----+---------+----------------+
| id | int(10) unsigned | NO | PRI | NULL | auto_increment |
| name | varchar(191) | NO | | NULL | |
| email | varchar(191) | NO | MUL | NULL | |
| password | varchar(191) | NO | | NULL | |
| remember_token | varchar(100) | YES | | NULL | |
| last_logged_in_at | timestamp | YES | | NULL | |
| enabled | tinyint(1) | NO | | 1 | |
| created_at | timestamp | YES | | NULL | |
| updated_at | timestamp | YES | | NULL | |
| deleted_at | timestamp | YES | | NULL | |
| locale | varchar(191) | NO | | en-GB | |
+-------------------+------------------+------+-----+---------+----------------+
11 rows in set (0.00 sec)
SOLVED - See my GUIDE
where is your GUIDE?
Showing 1 to 3 of 3 discussions