patchy :)
With chx's help we found a bug when trying to field_update_* while field_storage_default is set to mongodb field storage.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | file.crud_.inc_.patch | 682 bytes | litwol |
| #1 | field_storage_module.patch | 682 bytes | litwol |
| field_storage_module.wtf_.patch | 682 bytes | litwol |
Comments
Comment #1
litwol commentedComment #2
litwol commentedSorry for so many updated.. getting familiarized with submitting core patches.
Comment #3
litwol commentedNot sure why the patch was ignored.
Comment #4
litwol commentedHopefully that solves the mystery of the ignored patch.
Comment #5
chx commentedIt's one of those absolutely trivial, small mistakes that undermine the huge efforts to make the storage engine pluggable. But it's so easy to fix. The original post lacks an explanation:
the two variables need to be called the same and we opted on _default.
Comment #6
dries commentedGood catch, litwol and chx. Committed to CVS HEAD.
Comment #8
yched commentedWrong fix :-)
#693054: field_update_field() calls the wrong field storage backend