I'm try to review the commit about "building blocks for interception" and I have some questions about the design of this "super" feature :
Unai Zorrilla
- Why the Interception.AddInterceptor and not a new method in DbConfiguration (This is the same obsolete pattern like Database.SetInitializer<>).
- Is IDbCommandTreeInterceptor an interface designed for developper? Wich is the scenario to create a new interceptor based on this interface?
-
I think it might make sense to have configured at the same time more than one interceptor. e.g:
-
Create or use trace interceptors for debugging purposes ( console tracer ) and also have other interceptor for auditing.
-
Create or use trace interceptors for debugging purposes ( console tracer ) and also have other interceptor for auditing.
Unai Zorrilla