CiviCRM Community Forums (archive)

Hi,

On the sepa extension, we have two new entities (table/dao/api).

One of them is the mandate, that is linked to the contact, but also to a recurring contrib or a membership.

How to be sure this entity is properly updated too when a contact is deleted or merged?

Same question about ContributionRecur or Membership

As the mandate can be linked to a contribution, a recurring contribution or a membership already, I wanted to store this relationship a couple entity_id +entity_type so the sql level FK won't work.

But might be convinced to have several fields contributionrecur & contribution & membership

X+

Hi,

I've followed your suggested path 1, but cruder:

xml in the extension, symlink to civicrm, genGode within civicrm and symlink back the dao. The sql is copied by hand.

It isn't pretty but wasn't that much of a pain either. We'll see when we need to modify more often the schema. As an aside, found convenient to have the DAO in git, makes it easier to see I haven't copied back the sql.

https://github.com/Project60/sepa_dd

I don't have any opinion on doctrine, but I'm ready to bet I'll like it better than pear db_object.

IMO the tricky part will be to modify the BAO to "oo properly" inherit from the DAO and override the CRUD methods instead of creating static separate ones.

I'll keep your wiki in mind and come back to you once I've dug more into my extension.

To answer my own question, I'm guessing with hooks on merge, post and delete, I should be able to keep the new entity type in sync with the core ones.

X+