In strict mode, MySQL cannot accept an empty string when a field's "not null" property is set to TRUE. This can cause MySQL errors to be thrown in certain situations.

As far as I know there is no downside to setting 'not null'->FALSE, many CCK core fields do that now.

Patch attached, this is my second patch submission! Let me know if you need anything :)

CommentFileSizeAuthor
email.module.patch448 bytesgdd
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mh86’s picture

mh86 CreditAttribution: mh86 commented
Status: Active » Fixed

I added a default = "''" to the database column settings, like it is done in the text module. This fixes the problem, although I didn't write an update script to fix the already existing database columns..

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.