c2c-oerpscenario team mailing list archive

["Olivier Dony \(OpenERP\)" <772522@xxxxxxxxxxxxxxxxxx>]

(converting to a question, as this is not really a bug)

** Summary changed:

- [trunk][6.0] osv_memory column handling 
+ osv_memory classes seem to share their _columns?

** Changed in: openobject-server
       Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/openobject-server/+question/158036

-- 
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/772522

Title:
  osv_memory classes seem to share their _columns?

Status in OpenERP Server:
  Invalid

Bug description:
  Before I put together a more complicated scenario, maybe someone can
  explain the behaviour I'm seeing if it isn't a bug.

  I have two osv_memory wizards in separate classes which create dynamic
  forms. If I launch WizardA and then launch WizardB, the columns from
  WizardA are now attributes of WizardB as well. So if I print
  self._columns when launching WizardB, I'll see all of it's columns
  plus WizACol1, WizACol2, etc, etc. These don't show up on the form
  itself, but I believe it's causing a couple of issues elsewhere for
  me.

  So... why is WizardB being instantiated with WizardA's columns? The
  columns (should) belong to WizardA, not WizardB or their parent class
  osv_memory. Am I missing something?

  Let me know if a test module is required to demonstrate, or if I'm
  simply missing something obvious. Thanks!