masarati@aero.polimi.it wrote:

In order to support back-config in back-meta, I think each target's configuration should be in a specific child of the database's entry, because target configuration is way too complex to be stored in a single attribute.

I'm not sure how this can be easily accomplished in back-config.

I think this should be much like each child entry in a chain config. Define a new Cft_Misc table for the child entries.