Sorting on none classic_write field

Error

Wrong field name (complete_name) in order!

added 1 deleted label

This is because sort on fields function doesn't work. In fact it doesn't work
for all fields that is not _classic_write (means store in the table of the object).
So there is two options:
- Send to the client the field that can be sorted and disable the sort on those
that can not.
- Don't raise an exception when trying to sort on field that can not.
What do you think?

assigned to @ced

added tryton trytond type::behavior + 1 deleted label and removed 1 deleted label

Le Wed, 04 Jun 2008 23:38:02 +0200,
Cédric Krier <issue_tracker@tryton.org> a écrit :

>
> Cédric Krier <cedric.krier@b2ck.com> added the comment:
>
> This is because sort on fields function doesn't work. In fact it doesn't work
> for all fields that is not _classic_write (means store in the table of the
> object). So there is two options:
> - Send to the client the field that can be sorted and disable the sort on
> those that can not.
> - Don't raise an exception when trying to sort on field that can not.
> What do you think?

Imho option two will mislead the user, because iirc when one clic on the column
name, the query is re-run on the db (and possibly fetch items that were not on
the screen). Maybe the clever solution is to provide the sorting mechanism if
the client know that all the list has been fetch (20000 items by default) and
do nothing if not.

>
> ----------
> assignedto: -> ced
> component: +tryton, trytond
> nosy: +bch, ced
> status: unread -> chatting
> type: -> behavior
>
> _______________________________________________
> Tryton issue tracker <issue_tracker@tryton.org>
> <https://bugs.tryton.org/roundup/#64>
> _______________________________________________

Ok, I understand the problem. Isn't it possible to sort such non _classic_write
Fields on clientside. Or takes this a to long time?

If there is too much records on the list, it can become very expensive.
Because the client needs to read all the records.
I think we can add an new attributes to the fields that are not sortable, to
force the search function to use it.
Example:
For ir.ui.menu complete_name, we can add the attributes that it must use the
name field of the table to sort.

Fix with changeset 9c1b3c22f280

added 1 deleted label and removed tryton + 1 deleted label

closed

mentioned in issue #73 (closed)