Comment 3 for bug 371367

In my opinion, the domain must not work on a one2many field. A domain on
the object should be seen like a constraint, which is probably not what
you want.

A domain on the client side can be seen like a filter. So, if something
has to be changed, it's only on the client side. So, I put this as a
whishlist for now on. Please note that you can define your own field
that implement the domain. The module project_gtd does this if you need
an example.

<email address hidden> wrote:
> this bug also effects me.
> i'm trying to include the attachments list for an object in a form.
>
> eg.
> 'attachments': fields.one2many('ir.attachment','res_id','Attachments', domain="[('res_model','=','test.job')]" ),
>
> the domain filter seems to be ignored.
>

--
Fabien Pinckaers
CEO Tiny - OpenERP Editor
Chaussée de Namur 40
B-1367 Grand-Rosière
Belgium
Phone: +32.81.81.37.00
Fax: +32.81.73.35.01
Web: http://openerp.com

Great Achievements Start With Tiny Investments
   -- Marty, 2005