Re: Entity Framework - the lay of the land

On Fri, 16 Sep 2016 at 09:55 David Apelt wrote: > What type of projects is EF not suitable for? > Ones that run on computers. *Mr Connors thinks back to all the times he's been told he is wrong on this list for saying ORMs and their ilk are sh!t* David. -- David

Re: Entity Framework - the lay of the land

Using something like PetaPoco makes that pretty easy. > What about the classical problem of "impedance mismatch". You have to > carefully maintain DataSets or similar and use DataAdapter to fill them, > then writing data back is a circus trick with the ADO.NET classes. Then > they invented

Re: Entity Framework - the lay of the land

On Fri, 16 Sep 2016 at 10:33 Greg Keogh wrote: > What do you suggest as an alternative? >> >> Writing stored procedures. >> > > What about the classical problem of "impedance mismatch". You have to > carefully maintain DataSets or similar and use DataAdapter to fill them, >

RE: Entity Framework - the lay of the land

Or Dapper (https://github.com/StackExchange/dapper-dot-net) From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Craig van Nieuwkerk Sent: Friday, 16 September 2016 12:40 p.m. To: ozDotNet Subject: Re: Entity Framework - the lay of the

Re: Entity Framework - the lay of the land

> > The people who think that ORMs are a good idea have a code-centric view of > the world. > Stored procs! Here's the black hole of the argument. To me it's a simple reductionist problem... Clean-shaven code-centric people write real-world apps. Beardy DBAs design databases. Coders need

Entity Framework - the lay of the land

The great Greg Low recently posted on facebook about some frustrations with Entity Framework. So, when I'm asked a question starting with this: The root of our problem at the moment is that Entity Framework (v6.1.3) is choosing to cast datetime parameter values to datetime2 and then I can

Re: Entity Framework - the lay of the land

> > What do you suggest as an alternative? > > Writing stored procedures. > What about the classical problem of "impedance mismatch". You have to carefully maintain DataSets or similar and use DataAdapter to fill them, then writing data back is a circus trick with the ADO.NET classes. Then they

Re: Entity Framework - the lay of the land

Entertaining reply, as always David. [] made my morning. From: ozdotnet-boun...@ozdotnet.com on behalf of David Connors Sent: Friday, 16 September 2016 8:50:30 AM To: ozDotNet Subject: Re: Entity Framework -

Re: Entity Framework - the lay of the land

Document/Object DBs are kind of the solution for that, however, they still need to be managed. Grow a beard and become "full-stack". On Fri, Sep 16, 2016 at 11:56 AM, Greg Keogh wrote: > The people who think that ORMs are a good idea have a code-centric view of >> the world.

Re: Entity Framework - the lay of the land

PetaPoco or Dapper are not really an ORM like EF or NHibernate. You can write SQL or a stored proc and all it really does is map it to a POCO for ease of use in the C# code. I have not really touched a DataSet or DataAdapter directly for years. On Fri, Sep 16, 2016 at 10:51 AM, Greg Keogh

Re: Entity Framework - the lay of the land

> > What type of projects is EF not suitable for? >> > Ones that run on computers. > What do you suggest as an alternative? *GK*

Re: Entity Framework - the lay of the land

Even full stack has its problems. It's that whole "generalist" vs "specialist" argument - sure you can do a bit of everything, but in doing that, can you actually devote yourself to becoming a master in something? Pretty hard to do. It's yet another flaw in Agile I think. And that said, that's

Re: Entity Framework - the lay of the land

On Fri, 16 Sep 2016 at 10:08 Greg Keogh wrote: > What type of projects is EF not suitable for? >>> >> Ones that run on computers. >> > > What do you suggest as an alternative? > Writing stored procedures. David. -- David Connors da...@connors.com | @davidconnors | LinkedIn

Re: Entity Framework - the lay of the land

> > Using something like PetaPoco makes that pretty easy. > Okay, I never saw that before. It's still and ORM, albeit a small one. At a glance at the home page, you're coding SQL statements inside code (tight coupling), it's not a LINQ provider at all, and it uses T4 templates (like EF does

Re: Entity Framework - the lay of the land

They did it to reduce the number of errors found at runtime. The errors are found at compile time with orms. Dapper is another micro-orm that's worth looking at. On 16 Sep 2016 10:40 AM, "Craig van Nieuwkerk" wrote: > Using something like PetaPoco makes that pretty easy. > >

Re: Entity Framework - the lay of the land

I haven't had significant problems that I haven't been able to fix. That said, I think they're marking the current as Stable and just working on features of EF Core now, which isn't as complete by far yet. On Fri, Sep 16, 2016 at 10:40 AM, Craig van Nieuwkerk wrote: > Using

Re: Entity Framework - the lay of the land

> > > >> What can bridge the "impedance" gap? Something has to. >> > > I agree. It is called effort. > Come on David ... *effort* into what exactly? What tool, technology, kit, gizmo? I need more detail. I'm a coder. I've got to drag stuff in and out of databases that I don't own and didn't

Re: Entity Framework - the lay of the land

On Fri, 16 Sep 2016 at 13:36 Greg Keogh wrote: > >> >>> What can bridge the "impedance" gap? Something has to. >>> >> >> I agree. It is called effort. >> > > Come on David ... *effort* into what exactly? What tool, technology, kit, > gizmo? I need more detail. I'm a coder.

Re: Entity Framework - the lay of the land

If your project has a database and you are not using a Database Project you are missing out, and causing yourself a lot of unnecessary pain. It basically just organises your schema files to make them easy to maintain, like cs files in a c# project. It has tools to do comparisons and schema updates

Re: Entity Framework - the lay of the land

On Fri, 16 Sep 2016 at 11:56 Greg Keogh wrote: > The people who think that ORMs are a good idea have a code-centric view of >> the world. >> > > Stored procs! > I know, right? Finally, someone who shares my enthusiasm! [ ... ] > Databases are unlikely to have a structure