Right now we have 1:N (T_LOOKUP with CARDINALITY_SINGLE) and N:M (T_LOOKUP with CARDINALITY_MULTIPLE). We lack some kind of a N:1 (a reversed 1:N) relationship.

Example: brand 1:N model. Right now it is possible to use a 1:N lookup in model and assign the brand to the model. In many cases, e.g. to reduce the form editing effort, it makes sense to allow assigning models to brands in the brand editing form. Supporting this should be possible in dbWebGen