On 2018-01-23 05:50, Maxime Richez wrote:
> > For now, I think the Function field is the only option. The searcher
> > should probably have to return a clause like [('id', 'in', query)].
> > This is not optimal but it should work.
>
> 2 questions:
>
> - In the case of the function field is only used in a treeview for
> filtering data (just for display), isn't better to define a new
> modelview based on a query (for example:
> https://bitbucket.org/zikzakmedia/trytond-product_quantity_by_location/src
> ) Would it be more optimal ?
A new model means new views, new access rights etc. Also module that
extend the base may need to be aware of this new model.
> - What about the search function if one of the field to compare with
> another field is already a function field (for example product
> quantity field)? Is the only way of doing the search is still the
> query (that would be very complex in the case of quantity field,no ?)
> ?
Of course you can construct the domain by evaluating the records in
Python. But it will work only if you evaluate a small list of records.
Larger one will require to write a complex SQL query.
--
Cédric Krier - B2CK SPRL
Email/Jabber: [email protected]
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/
--
You received this message because you are subscribed to the Google Groups
"tryton" group.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tryton/20180123142004.GJ4226%40kei.
