Needs work
Project:
Computed Field
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Mar 2011 at 21:09 UTC
Updated:
23 Aug 2015 at 16:20 UTC
Jump to comment: Most recent
computed field declares that it will save not null as 0, then uses FALSE. Probs an easy fix, no?
column field_my_field - difference on: not null
declared: array('description' => t('TODO: please describe this field!'), 'type' => 'numeric', 'not null' => 0, 'precision' => '32', 'scale' => '2')
actual: array('description' => t('TODO: please describe this field!'), 'type' => 'numeric', 'not null' => FALSE, 'precision' => '32', 'scale' => '2')
best
Comments
Comment #1
Anonymous (not verified) commentedAm also seeing this:
Comment #2
claudiuv commentedThis bug is also in the 7.x-1.0 version
Comment #3
WorldFallz commentedmarked #2405839: field_sql_storage mismatch in schema module as dupe. Updating version as any fix would be rolled for d7 first, then backported.
Comment #4
WorldFallz commentedChanging:
to
In the .install file fixes the mismatch, but I'm not sure that's the 'correct' (clean) way to fix it.
It stems from the fact that the 'Not Null' setting for computed fields is 1 or 0 (checkbox) but schema api is looking for TRUE/FALSE.
The better way to fix this would probably be to ensure the value of the checkbox is translated from 1/0 to TRUE/FALSE when saved.
Comment #5
ram4nd commented