← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 715749] [NEW] [trunk] [5.0] [6.0] keep ids order on read method with an _inherits object

 

Public bug reported:

On v.5 and v.6 trunk.

When you give a list of ids on read function of an _inherits object
(like product.product), the read function returns automatically a list
of dictionnaries sorted by id (for product.product) even if you give a
not sorted list of id.

To see that, on a new db with demo data, create a XML-RPC script which
search all products with 'pc' in their name. This search function
returns you a list of ids sorted by id. Take this list of ids and sorted
it again with the biggest id at first and the smallest at last.

Give this new sorted list to the read function and see the result of
this function : the list of result is sorted by id (with the smallest id
at first).

It's a bug because the read function doesn't keep the order of ids give
to the function.

** Affects: openobject-server
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/715749

Title:
  [trunk] [5.0] [6.0] keep ids order on read method with an _inherits
  object

Status in OpenERP Server:
  New

Bug description:
  On v.5 and v.6 trunk.

  When you give a list of ids on read function of an _inherits object
  (like product.product), the read function returns automatically a list
  of dictionnaries sorted by id (for product.product) even if you give a
  not sorted list of id.

  To see that, on a new db with demo data, create a XML-RPC script which
  search all products with 'pc' in their name. This search function
  returns you a list of ids sorted by id. Take this list of ids and
  sorted it again with the biggest id at first and the smallest at last.

  Give this new sorted list to the read function and see the result of
  this function : the list of result is sorted by id (with the smallest
  id at first).

  It's a bug because the read function doesn't keep the order of ids
  give to the function.





Follow ups

References