Is cascading delete or update supported in LLBLGenPro 2.6 ?

Cascade Updates are supported.

myEntity.Save(True) <- True Flag is for Recursive Save.

I have Cascade Delete working. Supports both In-Memory & Database Deletes. Supports both Transaction & Unit Of Work. Determines proper delete commit order automatically.

Ryan

When you say CascaseUpdate and Delete are you refering to the DB server performing the Update/Delete for you based on the PK/FK relationships between the tables? or, as Ryan indicated in his message, do you mean that LLBLGen generates the updates/deletes for you on the client side ?

Matt

MTrinder wrote:

When you say CascaseUpdate and Delete are you refering to the DB server performing the Update/Delete for you based on the PK/FK relationships between the tables? or, as Ryan indicated in his message, do you mean that LLBLGen generates the updates/deletes for you on the client side ?

Matt

If I read a collection of orders and delete one of them and save the list, I expect that the orderlines are deleted also.

Please read this: Tracking entity remove actions

Walaa wrote:

Please read this: Tracking entity remove actions

When reading this, my "scenario" can not be easly executed....

I see, I didn't underrstand your question well.

If I read a collection of orders and delete one of them and save the list, I expect that the orderlines are deleted also.

Why don't you define the cascade delete at the database level?

Walaa wrote:

I see, I didn't underrstand your question well.

If I read a collection of orders and delete one of them and save the list, I expect that the orderlines are deleted also.

Why don't you define the cascade delete at the database level?

Well.. in fact that is defined at database level already . I want to make sure that LLBLGenPro can handle this kind of DB-handling.

If you have a graph in memory and you deleted an order and the database deleted the related orderlines, then you should refetch the graph again. (Refresh the graph in memory).

Oherwise database cascades should have nothing to do with LLBLGen Pro.

Walaa wrote:

If you have a graph in memory and you deleted an order and the database deleted the related orderlines, then you should refetch the graph again. (Refresh the graph in memory).

Oherwise database cascades should have nothing to do with LLBLGen Pro.

So LLBLGenPro has no mechanism in its own runtime code that can handle this... that is strange. Let say that a DBA adds a cascading rule to the database, then the code has to be rebuilt to get it work in client code.

So LLBLGenPro has no mechanism in its own runtime code that can handle this

What exactly that you want LLBLgen to handle?

Walaa wrote:

So LLBLGenPro has no mechanism in its own runtime code that can handle this

What exactly that you want LLBLgen to handle?

Well... after some thinking about the best way is that the database handles the cascading delete, and in the code you already have no related entities in hand because the parent entity is already deleted from the list

Exactly.