Proteus behaves different than GUI?

[htgoebel (Hartmut Goebel)]

While working on this issue quoted below, I added a doc-test to check this regression. Anyhow, while this test does the same as in the GUI (create a Member, add a party, save the member; no other data entered), the doc-test does not fail: After saving member1.code is None, while when using the GUI, it is the empty string.

Is this intented behavior? Anything missing in my regression-test?

@htgoebel

Mittelab’s implementation of “association” (see Association blueprint) has I minor issue, I try to solve: One can not have two Members in “draft” state. This is caused by the fact that when saving a Member, it will get code “” (empty string) - anyhow code is defined as “unique”. This inhibits saving a second Member in “draft” state.

This is the doc-test to check the regression (shortened here, but you get the idea):

Create first member::

   >>> Member = Model.get('association.member')
   >>> member1 = Member()
   >>> member1.party = party1
   >>> member1.save()

Create a second member - this failed due to ``code`` being an empty
string instead of ``NULL``::

   >>> member2 = Member()
   >>> member2.party = party2
   >>> member2.save()

I would expect member2.save() to fail, as it would when adding a new “Member” in the GUI. Anyhow it does not.

[ced (Cédric Krier)]

GUI can not display None as code can.

[htgoebel (Hartmut Goebel)]

That’s fine. But why is the code an empty string when saving via GUI, but None when saving via proteus? I’d expect both to create the same value (no matter which one, as long at it is the same)

[ced (Cédric Krier)]

Because we can with proteus and can not with GUI.