76

Re: Code First + SQL Triggers

ViPRos wrote:

IQuerable it is possible to return is part NET

What for, if it is possible on IQueryable to do the class typified specifications? Pieces LINQ of requests to the data, scattered on classes look not much better spread SQL.

77

Re: Code First + SQL Triggers

hVostt;
I mean that on a science  reset IQuerable cannot be qualified as an error and all.

78

Re: Code First + SQL Triggers

Calabonga wrote:

it is passed...
You do not catch an essence. Not only a DB. Specific implementation of a repository can quite work with indirect service.
Or not only with SQL a DB, but also with MongoDB. Or with Key/Value storage: Couchbase, Redis.
It is possible  such implementation IRepository that the data will be searched at first in local storage, then in the distributed cache, in a DB and if anywhere is not present to request indirect service, to put in a DB, the distributed cache and storage:-Q

79

Re: Code First + SQL Triggers

And thus the principle of uniqueness of responsibility will not be broken:-Q

80

Re: Code First + SQL Triggers

ViPRos wrote:

hVostt;
I mean that on a science  reset IQuerable cannot be qualified as an error and all.

The judgement that should be returned IEnumerable, instead of IQueryable prevails. And for me all one. And and so - it is not true. Requests should be separately that they could be tested.

81

Re: Code First + SQL Triggers

hVostt;
it is clear that, IEnumerable less dangerous piece, than IQueryable. But formally rolls on all canons .

82

Re: Code First + SQL Triggers

ViPRos wrote:

Podspudno is clear that, IEnumerable less dangerous piece, than IQueryable. But formally rolls on all canons .

Yes not, does not roll. Transited)

83

Re: Code First + SQL Triggers

hVostt;
Apprx.

Posts [ 76 to 83 of 83 ]

Pages Previous 1 2 3 4

You must login or register to post a reply