Is .NET Entity Framework still cool? Is .NET Entity Framework still cool? - Page 2
Page 2 of 2 FirstFirst 12
Posts 11 to 15 of 15
  1. #11

    My post count is Majestic

    d000hg's Avatar
    Join Date
    Dec 2007
    Location
    My house
    Posts
    32,189

    Default

    Quote Originally Posted by cannon999 View Post
    You don't know what you are talking about bro.
    This is a professional forum not General. Keep it in your pants. Bro.

    Sent from my ONEPLUS A6003 using Tapatalk
    Quote Originally Posted by MaryPoppins View Post
    I'd still not breastfeed a nazi
    Quote Originally Posted by vetran View Post
    Urine is quite nourishing

  2. #12

    My post count is Majestic

    d000hg's Avatar
    Join Date
    Dec 2007
    Location
    My house
    Posts
    32,189

    Default

    Quote Originally Posted by minestrone View Post
    Does nHibernate get used much in the .NET market?
    I feel like it never really caught on

    Sent from my ONEPLUS A6003 using Tapatalk
    Quote Originally Posted by MaryPoppins View Post
    I'd still not breastfeed a nazi
    Quote Originally Posted by vetran View Post
    Urine is quite nourishing

  3. #13

    Super poster

    woohoo's Avatar
    Join Date
    Nov 2007
    Location
    In the country
    Posts
    4,334

    Default

    Quote Originally Posted by cannon999 View Post
    You don't know what you are talking about bro.
    You could be correct but the lack of detail and arguments in your reply dont really enlighten anyone.

  4. #14

    Richer than sasguru

    DimPrawn's Avatar
    Join Date
    Jul 2005
    Location
    Brexit Britain
    Posts
    34,752

    Default

    Quote Originally Posted by woohoo View Post
    Never found it an issue with embedded sql, you tend to organise the repositories so they make sense. 80% of your work is simple update/insert/delete/fetch and you can use contrib so this basic sql is done for you.

    It's one of those if you can write decent sql and can organise a piss up in brewery you can successfully use Dapper or most other micro-orms.

    Dapper does have it's limitations, same for repository pattern but this crap about magic strings is nonsense.
    What I mean really is that with the Linq 2 Db approach, the complier checks your Linq, with embedded SQL + parameters it is easy to make mistakes and if you change the DB to a different vendor then the SQL might need to change.

    I'm not slating Dapper, I've used it and I like it, was just pointing out to +/- points to consider.

  5. #15

    Super poster

    woohoo's Avatar
    Join Date
    Nov 2007
    Location
    In the country
    Posts
    4,334

    Default

    Quote Originally Posted by DimPrawn View Post
    What I mean really is that with the Linq 2 Db approach, the complier checks your Linq, with embedded SQL + parameters it is easy to make mistakes and if you change the DB to a different vendor then the SQL might need to change.

    I'm not slating Dapper, I've used it and I like it, was just pointing out to +/- points to consider.
    No, fair enough and didnt mean to be defensive though on re-reading my reply i was quite harsh, apologies.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •