Please do come and have a talk with my (pointy-haired style) boss :) .
I take it you think stored procedures are generally good (at least that's what I think). But some people still believe that they'll migrate database architecture or some such. Also, some ORM's aren't fit for the task and give a bad name (Microsoft's Entity Framework v1 was especially horrible)
I'm definitely out of touch and I spend way too much time working with Microsoft SQL, but do people treat relational databases as "a crazy aunt" as Fowler says? (I still haven't tried NoSQL)
Re: SPs, no, I meant people used to say all your data access should be through SPs, which seemed to turn about 5-7 years ago as the general consensus moved to parametrized queries and freedom from DBAs overseeing your changes. I haven't seen anyone say that in a long time now. I used to use them for complicated TSQL and helper functions, like some crazy recursive tree building stuff, but these days I haven't actually written one now in a couple of years.
On a more individual level I'm also now finding myself even shying away from complicated SQL queries. I'm finding these days they're unnecessary 90% of the time. Often it's actually faster and more maintainable to pull out a larger amount of data and then do the more specific calculations in code. Even with good indexes, etc.
Heh, I'm probably 15 years behind then :) . Thank you for the reply :)
I strongly dislike writing "strings with sql" inside my code, though I do use parametrized queries these days.
I do appreciate freedom from DBAs as a feature :) but I have access to my stored procedures these days (though I don't know for how much longer).
I work for an insurance company with an awful legacy database structure, with mnemotechnic table names like S0001... to S99999, and disregard for naming conventions or even normalization sometimes. It's not making me a better developer :( unless learning by bad examples counts.
I take it you think stored procedures are generally good (at least that's what I think). But some people still believe that they'll migrate database architecture or some such. Also, some ORM's aren't fit for the task and give a bad name (Microsoft's Entity Framework v1 was especially horrible)
I'm definitely out of touch and I spend way too much time working with Microsoft SQL, but do people treat relational databases as "a crazy aunt" as Fowler says? (I still haven't tried NoSQL)