No problem, that's an architectural question. When starting a new application today, referring to the 3-tier standard model, I have an almost empty data layer, which does almost only returning IQueryable<>, and the rest of the request can be done from the service/business layer. This way, you can use without any difference any Linq provider, since all you require is an IQueryable<> provider. Of course, you still need to add or delete entities, but this can stay in the data layer (and still be small).
Pascal. jabber/gtalk: [email protected] msn: [email protected] On Wed, Mar 11, 2009 at 17:08, Giacomo Tesio <[email protected]> wrote: > I've found, it was a stupid question. Sorry! > > Patience with me, will give you the Paradise! :-D > > > Giacomo > > > > On Wed, Mar 11, 2009 at 4:33 PM, Giacomo Tesio <[email protected]> wrote: > >> Why DbLinq has it's own implementation of such types? >> >> Is it about their implementation? >> >> >> Giacomo >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
