Searching res.partner using a category should do a child_of search

Bug #522528 reported by Numérigraphe
36
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Odoo Server (MOVED TO GITHUB)
Confirmed
Wishlist
OpenERP's Framework R&D
Nominated for Trunk by Numérigraphe

Bug Description

Partner tags can be organized in a hierarchy. This a useful feature but we can't make the full out of it because we can't use child_of.
It would also improve the search views.

Example: in the current 7.0 demo dataset we have a category "Partner" with a subcategory "Partner / Telecom".
But if we tag a partner with "Partner / Telecom", it won't show up when we search for the tag "Partner".

Revision history for this message
Numérigraphe (numerigraphe) wrote :

Here is a bzr merge file with a patch to add this feature.
Lionel.

description: updated
Changed in openobject-server:
importance: Undecided → Wishlist
Revision history for this message
Fabien (Open ERP) (fp-tinyerp) wrote :

parent_store must be used whenever we have big structures ? I don't htink it's usual to have very big structures for partners categories. I don't see the goal of doing this ?

Changed in openobject-server:
status: New → Invalid
Revision history for this message
Numérigraphe (numerigraphe) wrote : Re: [Bug 522528] Re: Use parent_store in partner categories

Le 08/11/2010 22:08, Fabien (Open ERP) a écrit :
> parent_store must be used whenever we have big structures ? I don't
> htink it's usual to have very big structures for partners categories. I
> don't see the goal of doing this ?
>
> ** Changed in: openobject-server
> Status: New => Invalid
>
>
In our case that feature was demanded for a small tree.
Unless you store the parents, you can't search a branch - like "all
customers" in this example :
- customers
   - recent
   - old
- suppliers
Please correct me if I'm wrong of course.
If it can't be in the core addons I can push a module for that.
Lionel.

Revision history for this message
OpenERP buildbot (openerp-buildbot) wrote :

On Monday 08 November 2010, you wrote:
> parent_store must be used whenever we have big structures ? I don't
> htink it's usual to have very big structures for partners categories. I
> don't see the goal of doing this ?
>

++

I would like to add that parent_store may be redundant if we ever include the
pg84 enhancements. Storing the parent_left and parent_right may speed up
_reading_ of the tree, but will put a heavy burden on writing or modifying the
tree. Postgres, as of 8.4, can offer an alternative efficient way to perform
searches in tree-structured data.

--
Say NO to spam and viruses. Stop using Microsoft Windows!

Revision history for this message
Numérigraphe (numerigraphe) wrote : Re: Use parent_store in partner categories

I'll mark this "opinion", let's wait and see after 6.0 is released.
Lionel

Changed in openobject-server:
status: Invalid → Opinion
Revision history for this message
Numérigraphe (numerigraphe) wrote :

qdp reported in Bug #676392 :
"""
The menu "Partners by Categories" isn't there anymore because we should use the category criterion on the search view. But this is not doing the same as currently the search isn't doing a child_of operation but a classic equal operation.

Thus, we should overwrite the search on res.partner in order to deal with above case.
"""

Changed in openobject-server:
status: Opinion → Confirmed
description: updated
Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

To be considered for post-v6 release.

Changed in openobject-server:
assignee: nobody → OpenERP's Framework R&D (openerp-dev-framework)
summary: - Use parent_store in partner categories
+ search catgeories on res.partner should do a child_of
summary: - search catgeories on res.partner should do a child_of
+ Searching res.partner using a category should do a child_of
summary: - Searching res.partner using a category should do a child_of
+ Searching res.partner using a category should do a child_of search
Revision history for this message
Numérigraphe (numerigraphe) wrote :

In lp:~numerigraphe/openobject-server/trunk-search-category-child-of, I tried to fix this bug by adding an "operator" attribute to the search view, as the docs suggest should be possible (http://doc.openerp.com/v6.0/developer/2_6_views_events/views/search_view.html#fields).
But it does not fix the problem, so I guess there is a deeper issue here.
Any advice on how this should be fixed?
Lionel.

Revision history for this message
Numérigraphe (numerigraphe) wrote :

This has been once again reported, rejected, disputed and eventually accepted as a bug in Bug #1006317.

description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.