For testing, I did a new install drupal 6.24 English
I add cck module last version, I enable text and integer.
I add a new content type with an integer field, not required.
I add 3 contents (not important).
I migrate from D6 to D7, core, then cck
When I add a new content of that content type, with no value for integer, I get :
PDOException: SQLSTATE[HY000]: General error: 1366 Incorrect integer value: '' for column 'field_entier_value' at row 1: INSERT INTO {field_data_field_entier} (entity_type, entity_id, revision_id, bundle, delta, language, field_entier_value) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6); Array ( [:db_insert_placeholder_0] => node [:db_insert_placeholder_1] => 6 [:db_insert_placeholder_2] => 6 [:db_insert_placeholder_3] => nicole [:db_insert_placeholder_4] => 0 [:db_insert_placeholder_5] => und [:db_insert_placeholder_6] => ) in field_sql_storage_field_storage_write() (line 448 of C:\Program Files (x86)\EasyPHP-5.3.8.1\www\cms\cmsd624en\modules\field\modules\field_sql_storage\field_sql_storage.module).
I ask here because since months there is no issue to that problem and for now, because of that, nearly all upgrades D6/D7 are stopped. For integer, it's easy to turn around problem by just giving a default value to zero, but for nodereference, it's not possible and problem is same as with integer.
Comments
Comment #1
xjmCan someone confirm whether this is reproducible with just Drupal core? If not, we should move it to the CCK queue. Thanks!
Comment #2
sahuni commentedCan someOne tell me if for him/her, it's working?
Comment #3
sahuni commentedWell,
If I go to content type management and I update that field (with no change) and save, after it's OK.
I update priority from major to normal, because I add that to my checklist, and will have nomore problem later on.
Comment #4
dkingofpa commentedI'm getting the error as well. However, this appears to be a duplicate of #1330952: Saving an Image field with an image that has undeterminable dimensions throws PDOException.
Comment #5
chipway commentedI don't think it's a duplicate as stated above.
Did you check your field definition for allowed values : We met a case where after d7 upgrade we add a field with allowed values like:
select|Select
0|Do
1|Done
2|postponed
Removing the first line was a first step (select is not an integer).
We add also term_reference field, for which re-saving the field parameters solved the issue.