← Back to team overview

c2c-oerpscenario team mailing list archive

Re: [Bug 709201] Re: No "code" field in "res.currency" object

 

On 21. 02. 11 13:05, Marco Dieckhoff wrote:
> I'm ok 

> with the solution Olivier described.
>
> But as "name" already get's confused again, wouldn't renaming the field
> to code (or isocode) and using _rec_name = "code" an option?
>
> When someone needs an additional long name, (like "US Dollar" in
> addition to USD), that could be done with a module, adding a
> translatable field like "description". Though I won't argue against
> having it in base.
>
> Maybe it's worth putting it on http://feedback.openerp.com/, if you need
> it.
>
this touches deeper levels of thought... :-)

have you heard about the KISS principle? it means just "keep it stupid
simple"!!
of course you can write a "module" for each field actually, but is that
really a solution? i feel that there is already an overkill with over
600 "modules", in the trunk +extra.

however, for a field in a table which NEVER gets large (the no. of
currencies is relatively small and constant) i see no issue in just
adding it.

just a thought, of course
regards,
bogdan

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/709201

Title:
  No "code" field in "res.currency" object

Status in Aeroo Reports for Open ERP:
  Confirmed
Status in OpenERP Modules (addons):
  Invalid
Status in OpenOffice.org Reporting Engine for OpenObject:
  Confirmed

Bug description:
  There is no code field in the res.currency object, which used to hold
  ISO 4217 (http://en.wikipedia.org/wiki/ISO_4217) code for the
  currency. ISO code is the only referable code for a currency, any
  other name is just user friendly representation and may vary from
  country to country, still they are not official names of the currency.

  Please do not disregard this defect as many modules depend on this
  code do find correct currency in a system.

  This defect is present in whole OpenERP's 6th version branch.



References