Revert 83282f2d for a cleaner sanitizing earlier in the generation of the error
message.
If the import is failing, the error message contains the value that is
problematic. Escape this value in case it contains '%'
The old-api model._all_columns contains information about model._columns and
inherited columns. This dictionary is missing new-api computed non-stored
fields, and the new field objects provide a more readable api...
This commit contains the following changes:
- adapt several methods of BaseModel to use fields instead of columns and
_all_columns
- copy all semantic-free attributes of related fields from their source
- add attribute 'group_operator' on integer and float fields
- base, base_action_rule, crm, edi, hr, mail, mass_mailing, pad,
payment_acquirer, share, website, website_crm, website_mail: simply use
_fields instead of _all_columns
- base, decimal_precision, website: adapt qweb rendering methods to use fields
instead of columns
A squashed merge is required as the conversion of the apiculture branch from
bzr to git was not correctly done. The git history contains irrelevant blobs
and commits. This branch brings a lot of changes and fixes, too many to list
exhaustively.
- New orm api, objects are now used instead of ids
- Environements to encapsulates cr uid context while maintaining backward compatibility
- Field compute attribute is a new object oriented way to define function fields
- Shared browse record cache
- New onchange protocol
- Optional copy flag on fields
- Documentation update
- Dead code cleanup
- Lots of fixes
ir.fields architecture turns out not to be a very good or simple fit,
especially as different widgets/fields need different granularity of
customizations. Having objects dedicated to each field type/widget
makes things simpler as it allows a conversion pipeline which can be
plugged into at any point.
bzr revid: xmo@openerp.com-20131007091556-03azc2mdhcb7kmwo
> many2one --> mettre <br/> si multi-line, html escape le reste (ex:
> adresse sur un event, on a du mettre dans un <pre> mais ce n'est pas
> bien)
> text --> mettre <br/> si multi-line, html escape le reste (ex:
> description d'un produit, à droite)
> char --> normalement pas de multi-line
> fields.binary --> t-field on image field ne semble pas fonctionner
> en écriture (la photo d'une fiche produit)
(validates that the binary field's content is image data by opening it
with PIL, then generates an <img> tag)
TODO:
> fields.float --> utiliser le digits pour formatter les decimals
> correctement (ex: prix d'un produit, à deux décimales)
> On aura aussi besoin d'un widget="currency", un peu comme dans la
> vue form du client web.
bzr revid: xmo@openerp.com-20130926133850-ab14h241q878jbom
command helpers create a single command, still need the list around commands
and the tests would have caught it, if I'd run them...
bzr revid: xmo@openerp.com-20121009070934-7i1hxuzumdu8x1jy
Python turns out to have changed the wording of the messages between 2.6 and 2.7
also, these messages need to be translatable *and* use the human-readable field name
bzr revid: xmo@openerp.com-20120927103452-cvgv3e8dsvcvnics
* although it does use an explicit external index, it turns out the
code is less complex
* the rewrapping of (many) iterators on top of one another ended up
blowing Python's stack during ``next`` calls, which Python does
*not* like
* added a 900-ish import test file to check for these things
bzr revid: xmo@openerp.com-20120925135955-oielhopegnefyctm
Martin Trigaux
Raphael Collet
Christophe Simonis
Denis Ledoux
Christophe Combelles
Christophe Simonis
Martin Trigaux
Mohammed Shekha (OpenERP)
Xavier Morel
Christophe Matthieu
Cecile Tonglet
Thibault Delavallée
Fabien Pinckaers
Olivier Dony