The big problem with this is that if two stored procedures feed the Foo type in C# and a developer changes one of the stored procedures to loop in a few more columns from the tables it queries and then adds those extra items as getsetters on Foo, the calls to the other, second stored procedure will break when the extra getsetters cannot be hydrated. In the app we are working on the team lead is a DBA and he argued in favor of a strict stored procedure approach not using Entity Framework whatsoever. In time another big personality argued for Entity Framework and we worked out a compromise that was somewhere horribly in-between. The pain point I mention rears its head all of the time. What is the fix? Make a new POCO for each sproc?
No comments:
Post a Comment