openerp-india team mailing list archive

[Raphaël Valyi - http://www.akretion.com <928424@xxxxxxxxxxxxxxxxxx>]

Heloo just a comment,
I check in our Brazilian localization: name and description are always
equal: so as for us we don't need a description field. Not sure how it is
for the others, may be worth asking officially.

Regards.

On Tue, Feb 7, 2012 at 8:00 PM, Ronald Portier (Therp)
<ronald@xxxxxxxx>wrote:

> Maybe we do not need a description.
>
> But this that take away from the fact the change breaks existing
> localizations for no apparent reason?
>
> And what about the argument that a unique constraint is added to a non
> required field?
>
> --
> You received this bug notification because you are a member of OpenERP
> Drivers, which is subscribed to OpenERP Addons.
> https://bugs.launchpad.net/bugs/928424
>
> Title:
>  [6.1, account] Tax description should not have uniqueness constraint
>
> Status in OpenERP Addons (modules):
>  New
>
> Bug description:
>  Hi,
>
>  since a couple of days, the uniqueness constraint on the field 'name'
>  on the Tax model (account.tax) has been swapped for a uniqueness
>  constraint on the field 'description' (see [1]). I do not believe that
>  this is correct, for the following two reasons:
>
>  - The description field is not a required field, and many
>  localisations do not use it. To have a uniqueness constraint on such a
>  field is meaningless.
>
>  - Other localisations such as the Dutch, German, Austrian and Canadian
>  naturally use the same description as a shorthand for similar taxes
>  that cannot occur together. In case of l10n_nl for instance, the same
>  description reflects the tax type and percentage for both taxes
>  payable and receivable. In the current state of the repository, it is
>  not possible to configure a chart of accounts anymore according to any
>  of these localisation modules.
>
>  Please revert the commit refered to in [1].
>
>  Cheers,
>  Stefan.
>
>  [1] http://bazaar.launchpad.net/~openerp/openobject-
>  addons/trunk/revision/6488
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-addons/+bug/928424/+subscriptions
>

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

Title:
  [6.1, account] Tax description should not have uniqueness constraint

Status in OpenERP Addons (modules):
  New

Bug description:
  Hi,

  since a couple of days, the uniqueness constraint on the field 'name'
  on the Tax model (account.tax) has been swapped for a uniqueness
  constraint on the field 'description' (see [1]). I do not believe that
  this is correct, for the following two reasons:

  - The description field is not a required field, and many
  localisations do not use it. To have a uniqueness constraint on such a
  field is meaningless.

  - Other localisations such as the Dutch, German, Austrian and Canadian
  naturally use the same description as a shorthand for similar taxes
  that cannot occur together. In case of l10n_nl for instance, the same
  description reflects the tax type and percentage for both taxes
  payable and receivable. In the current state of the repository, it is
  not possible to configure a chart of accounts anymore according to any
  of these localisation modules.

  Please revert the commit refered to in [1].

  Cheers,
  Stefan.

  [1] http://bazaar.launchpad.net/~openerp/openobject-
  addons/trunk/revision/6488

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