openerp-india team mailing list archive

["Olivier Dony \(OpenERP\)" <1070757@xxxxxxxxxxxxxxxxxx>]

Hello Paulius,

I agree that this behavior may be surprising and may constitute an
annoying limitation, but it was designed that way: the _order attribute
of OpenERP models is meant to be directly passed in the SQL query
without any extra processing, whereas the `order` parameter passed to
search() is post-processed to handle many2one and inherited columns.

The _order attribute is low-level, while the search order parameter is
high level.

This allows to use arbitrarily complex ordering clauses in _order,
combining any PostgreSQL operators like lower() substring(), coalesce(),
etc. These arbitrary expressions would be very hard to parse in order to
support many2one columns or inherited columns. It would also be quite
strange, because we would be mixing low-level SQL operators with high-
level OpenERP column definitions.

As a result, this is dangerous to change, and needs to support the
complex cases properly.

I will confirm your bug for trunk, as a nice-to-have feature (priority
Low), but this will not be changed in past stable versions, as it breaks
all the rules of our stable policy [1].

We can discuss this further on the merge proposal...

Thanks for reporting,

[1] http://doc.openerp.com/v6.1/contribute/11_bug_tracker.html#bug-management-policy
[2] BTW the merge proposal is not linked to the bug, perhaps you forgot to use --fixes when for your commit. See also our documentation about merge proposals: http://doc.openerp.com/v6.1/contribute/15_guidelines/contribution_guidelines.html#merge-proposal-guidelines

** Changed in: openobject-server
   Importance: Undecided => Low

** Changed in: openobject-server
       Status: New => Confirmed

** Changed in: openobject-server
     Assignee: (unassigned) => OpenERP's Framework R&D (openerp-dev-framework)

** Summary changed:

- [6.0, 6.1, trunk] Sorting object by many2one field fail 
+ [wishlist] _order should support sorting using inherited fields and many2one fields

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/1070757

Title:
  [wishlist] _order should support sorting using inherited fields and
  many2one fields

Status in OpenERP Server:
  Confirmed

Bug description:
  If object (e.g. sale.order) is sorted by many2one (e.g. _order =
  'user_id'), sorting is done by value of sale order table (user_id,
  integer) excluding many2one field value (e.g. user name).

  From the technical side I see that orm.py _generate_order_by method is
  not fully used when _search is done.

  One of fix is to set self.order for the _search function if it's order
  parameter is None.

  To reproduce bug:

  1. set _order = 'user_id' for the sale_order
  2. create user with name 'C'
  3. create user with name 'A'
  4. create user with name 'B'
  5. Create sale orders and assign each user to sale order
  6. Open sale_order list

  Result observed:
  Sale orders order are: C, A, B

  Result expected:
  Sale orders order are: A, B, C

  I've attached screenshot. Used trunk rev: 4504

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/1070757/+subscriptions