I agree, I’ll remove that.
I think I can leave this field out (I’ll add it on a separate module to satisfy my needs)
My idea (and please tell me if this can make sense), was that a member can have multiple subscription (so a
many2many relation in this context make sense).
One user case to support this is to have a main annual membership, and the have a monthly based fee.
Sorry, but i didn’t quite understand.
If you mean that there be an join/leave date on
association.membership, and the join/leave date of the member depends on that (just a function field) this will break down if I want add the many2many relation to membership. But most importantly this will not permit to register the join date/leave date for each member.