The nested call to replace_ending_clause must be pushed in the result instead
of concatenated because the clause can be OR-ed.
And pslice must remove depth from the length of the sting.
issue11477
review421151003
When the operator is 'in' and the value contains None, Field._domain_add_null
adds an equal operator against NULL. So this must be managed like the '='
operator.
issue9906
review332201005
The domain parser need to find the number of digit to display by analysing the
string format of the value. Some small values may be formatted as exponential.
issue9955
review347261002
c3 does not support moment but only string with a specific format.
We implement .toString on the moment prototype because form widgets does not
use Sao.Date nor Sao.DateTime. This ensures that calling .toString will always
return the ISO format.
And finally the x field type is retrieved from the model instead of the
attribute which is no more filled since changeset 2fc36d9e359b
issue9539
review296221002
We implement the same behavior as SQL with NULL which always returns NULL
except for IS operator. So the evaluation has the same result as the search.
issue8615
review290281002
Those branches of the domain should not prevent to compute a proper inverted
domain for the field as the other fields will be fixed later.
issue9200
review311191002
The server adds to the definition of the fields, the definition of relation
fields up to specific deep level.
The clients use this relation fields definition to extend the domain parser
with those fields using a dot notation. But those "dotted fields" are not
shown in the search filter to not bloat the popup as it is dedicated to
learning.
In addition, Dict fields are also filled with relation fields coming from the
keys defined in the schema model. As the size can very large, it is possible
to deactivate this feature from the configuration.
issue8293
review259391005
in operator on relation field must use list of ids. So the related rec_name
should be used instead because domain_parser always uses string as value.
issue3540
review271321002
Domain inversion on Reference field does not work when using the dotted
notation with a M2O field using child_of or parent_of.
To solve this we correctly compute the localization of child_of leaves when
using the dotted notation (which renders the inverse_leaf function useless).
But we must also ensure that the selection used by reference fields restrict
the choice to the right models.
issue7869
review60441002
The evaluation to True of constrained clause should only be done for inversion.
Also it should be valid even if a wrong value is defined in the context.
issue7603
review56331002
Cédric Krier