Integrity constraint violation: 1048 Column 'name' cannot be null about handesk HOT 7 CLOSED

Nice one hehe, we have two options

• Put a default name if none in the email
• Make the name nullable

from handesk.

I guess nullable is fine.

A default like "unknow" can cause a reply by a supporter - who is reading the name - like "Hello my Unknow"
So better nullable i think

from handesk.

Hello again ;)

the error occurt again in production - at the moment as a workaround i test

alter table requesters modify name varchar(191) null;

if you think we can leave the field nullable (side effect with forms and objects ???)

i can make a migraion to fix this error. What do you think ?

from handesk.

ops,
yes please, I'll merge it;, make it nullable and we will be ready to go :D

from handesk.

Just fixed this!

from handesk.

from handesk.

Column 'name' cannot be null

INSERT INTO ci_crud (name, email, created_at) VALUES (NULL, NULL, '21-01-06')

Filename: C:/xampp/php/htdocs/crud/crud_ci320/system/database/DB_driver.php

Line Number: 691
please give solution

from handesk.