← Back to team overview

openerp-expert-localization team mailing list archive

[Bug 928424] Re: [6.1, account] Tax description should not have uniqueness constraint


Hi Stefan,

I'm sorry for this problem. In fact, there was a problem with the
migration script and I think I pushed this patch by error.

I reverted the patch. Thank you so much for your useful feedback


You received this bug notification because you are a member of OpenERP
Localization Experts, which is subscribed to the bug report.

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

Status in OpenERP Addons (modules):
  Fix Released

Bug description:

  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].


  [1] http://bazaar.launchpad.net/~openerp/openobject-

To manage notifications about this bug go to: