Comment 17 for bug 1013636

Also I just would like to comment on the argument used to justify the
current bahavior: "one may want to save some record as draft without
lines". Well IMHO this is no valid justification as you could use it for
any other kind of mandatory field; for instance using the same argument you
could justify not checking if partner_id is present on a sale order
petexting youb may want to save a draft version of the order. And IMHO the
debate if that's a bug or an improvement is sterile, it's obviously a basic
feature to have, that makes at least as much sense as the CSS fluff being
invested on currently.
On Jul 22, 2012 7:45 AM, "Antony Lesuisse (OpenERP)" <email address hidden> wrote:

> Oh i didn't see the patch. What visual feedback is used to tell the user
> that the o2m is invalid ?
>
> --
> You received this bug notification because you are a member of OpenERP
> Drivers, which is subscribed to OpenERP GTK Client.
> https://bugs.launchpad.net/bugs/1013636
>
> Title:
> [6.1, trunk] One2many widget does not honour being 'required'
>
> Status in OpenERP Web:
> Confirmed
> Status in OpenERP GTK Client:
> Confirmed
>
> Bug description:
> Hi,
>
> both 6.1 and trunk do not signal correctly when a required one2many
> field is being left empty.
>
> An example from the base module is to go to Settings -> Technical ->
> Database Structure -> Models. Create a new model, but do not enter any
> fields. The model can be saved without an error message, even though
> Fields is a required field on ir.model.
>
> I would expect the client to raise an error 'The following fields are
> invalid: Fields'
>
> cheers,
> Stefan.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openerp-web/+bug/1013636/+subscriptions
>