Hello All,

OnFetchComplete does not seem to exist in the adapter model.

How can I add some logic "on fetch complete" of an entity?

Thanks,

Silat

Try OnFetchEntityComplete

This one does not exist for Entity.

If you want to add validation logic, add it to OnValidateEntityAfterLoad in the entity. What kind of logic do you want to add?

This is not really validation logic.

I need to do some processing before inserting into the DB(OnBeforeEntitySave) and after getting data from DB (OnFetch???).

In fact, I have an HTML field (on which I have fulltext search), therefore to enable the fulltext indexation, before inserting the data I am adding a blank around each tag.

Then, when I fetch it from DB, I have to : - remove all the extra blank. - set this field to IsDirty = false;

Because if I put directly <tag>Hello</tag> in my DB, then Hello will not be indexed.

I think that OnValidateEntityAfterLoad() would be a nice option. But if you see it does not belong there and it should be somewhere else, then I suggest it belongs to business logic and should be implemented in some manager class, from which you call a method just after you fetch the entity.

I found the following note a useful one to read(copied from LLBLgen Pro manual "Concepts - N-tier development"):

Business logic and where to put it Where to put your business logic code? The section Using the generated code goes more deeply into the question where Business Logic code can be placed in combination with the generated code. There are roughly three kinds of business logic or better: business logic rules:

1- Field oriented business logic rules. Example: ID > 0. 2- Entity wide oriended business logic rules. Example: Ship date >= order date 3- Cross entity oriented business logic rules. Example: Customer is gold customer if customer has purchased at least n orders in the last m months

In LLBLGen Pro, type 1 and 2 are done through Validator classes, which implement IValidator. Validator classes can be generated for each entity by enabling the task to generate them in the run queue when generating code, they're not generated by default. You can also opt for implementing the type 1 and type 2 code inside an entity, for example by using a partial class. Typically you then override the validation methods like OnValidateEntityAfterLoad() and similar methods. Type 3 are stored in classes placed on top of the generated code, so called manager classes which manage a process or sub- process. LLBLGen Pro offers several options for you to add type 1 and type 2 code to the generated code in a safe manner. Please consult Adding your own code to the generated classes for details.

Thanks Walaa,

I will put it into the manager classe together with the save.

Silat.