 [FIX] BufferedDataSet to not break the m2o read contract of returning a name_get format    BufferedDataSet simply shoves stuff read() or create()d in its cache,  but m2o is asymmetric: client writes a single id, but reads a pair of  [id, name].    Since create() and write() are async (by definition) it's the best  place to check if the data being written contains any m2o field, and  to fix those m2o values.
 [FIX] BufferedDataSet to not break the m2o read contract of returning a name_get format
 
 BufferedDataSet simply shoves stuff read() or create()d in its cache,
 but m2o is asymmetric: client writes a single id, but reads a pair of
 [id, name].
 
 Since create() and write() are async (by definition) it's the best
 place to check if the data being written contains any m2o field, and
 to fix those m2o values.

This, however, completely breaks o2m fields get_value(), and doesn't
even work correctly for create() calls.

Should probably not cache the same thing we put for creation or update
eh


akretion/openerp-web,havt/openerp-web,havt/openerp-web,havt/openerp-web,akretion/openerp-web,akretion/openerp-web,havt/openerp-web,havt/openerp-web