Using adapter, version 2:

Should a m:n link table have a surrogate pk or a composite one over the two fk's?

How does LLBLGen implement composite / aggregate relations? I.e. If an order is deleted, how should its orderlines be deleted - via manual code, automatic code, db referential integrity?

Thanks

Should a m:n link table have a surrogate pk or a composite one over the two fk's?

That's your call. Does not matter to LLBLGen Pro, as long as the PK-FK relations are defined.

How does LLBLGen implement composite / aggregate relations? I.e. If an order is deleted, how should its orderlines be deleted - via manual code, automatic code, db referential integrity?

All the above options are available: 1- db referential integrity on the DB level 2- via manual code on the BL level. 3- but in case of "automatic code", you will have to hook up some code in the DAL Level So I'd not call it automatic after all (this may appear as the same as the second option, but I wanted to differentiate between them according to the level of implementation)