Skip to Content
0
Former Member
Jun 03, 2008 at 03:31 AM

Persistency and transaction problem

17 Views

In CAF, if my model has a cardinality 0..1 (nullable in database), how can I make the generated create entity service to accept the parameters that are optional? I found that CAF will drop off those parameters by default.

Moreover, is it strange that both update and delete will accept a BO as parameter while the create is using parameters instead? Is there any rational behind?

At last, can someone give me a reference to the general overview of transaction management in CAF?

Thanks!