Ayende @ Rahien

Ayende Rahien commented on Querying Is A Business Concern: Sample

Tue, 13 Mar 2007 23:32:36 GMT

No problem. I am glad to know that we agree with each other.

Derick Bailey commented on Querying Is A Business Concern: Sample

Tue, 13 Mar 2007 23:30:56 GMT

This turned out to be a semantic misunderstanding on my part, not a design or implementation difference. My appologies for the misunderstanding.

Dim Blog As New ThoughtStream(me) commented on Querying Is A Business Concern: Sample

Tue, 13 Mar 2007 16:24:40 GMT

Ayende Makes The Statement that Querying Is A Business Concern. I have often made this same statement...

Ayende Rahien commented on Querying Is A Business Concern: Sample

Tue, 13 Mar 2007 13:33:37 GMT

Did notice that the query is in the authorization service? The only logic in the IsAllowed() method is in the query, so to test that I need a DB anyway. If I don't want that, I can mock the authorization service directly.

Derick Bailey commented on Querying Is A Business Concern: Sample

Tue, 13 Mar 2007 13:20:26 GMT

Ayende, The code that you post in your comment is what I would consider to be the mechanics - the service portion of the call - and should be hidden behind an interface. My basic reasoning for making this statement is encapsulation - to allow the mechanics of the query to change, without the semantics of the call changing. This becomes even more important in unit testing. If I am going to test the CRUD permissions of a Controller for a screen, I need to be able to mock the CRUD call to return an expected result, without having the real permission store set up and connected. public interface IPermissionService { public ICollection GetPermissions(); } public class PermissionService: IPermissionService { public ICollection GetPermissions() { return Repository.FindAll("query", parameters); } }

Ayende Rahien commented on Querying Is A Business Concern: Sample

Tue, 13 Mar 2007 05:11:57 GMT

@Derick, Can you define what is a query mechanics in this case? The code that I am using is: ICollection permissions = Repository.FindAll("query", parameters); return permissions.Count != 0

Ayende Rahien commented on Querying Is A Business Concern: Sample

Tue, 13 Mar 2007 05:10:03 GMT

@SteveG, Just the first query is using Linq, the other two are HQL queries. There are no real trade offs between the two queries, except for efficiencies. Yes, you can cache this query

Richard LOPES commented on Querying Is A Business Concern: Sample

Tue, 13 Mar 2007 04:41:01 GMT

I very much agree with the architecture proposed by Derick.

Derick Bailey commented on Querying Is A Business Concern: Sample

Tue, 13 Mar 2007 01:52:29 GMT

shouldn't the "process" of obtaining the permissions be the business logic, but the actual query mechanics be service logic? I believe there is a distinct difference between the two, although the implementation may join them via interface vs. implementation.

SteveG commented on Querying Is A Business Concern: Sample

Tue, 13 Mar 2007 00:01:44 GMT

Ayende, Although it might be inefficient, is there a tradeoff here depending on the situation? I wonder as well, does this Linq query get cached ? I do however agree with your comments, this is very much business logic!