|
Or you can roll your own.
|
|
|
|
|
Too busy with community engineering on CodeProject nowadays 
|
|
|
|
|
You mean rolling your own and posting an article about it? 
|
|
|
|
|
Quote: A nod's as good as a wink to a blind bat.
|
|
|
|
|
Yep, it's awesome!
They call me different but the truth is they're all the same!
JaxCoder.com
|
|
|
|
|
Do you mean something like
(from row in context.Person
where row.Name.Contains("foo")
select row).Take(10).ToList()
Do you (erroneously) "oppose it" to something like
context.Person.Where(x => x..Name.Contains("foo")).Take(10).ToList()
I guess I do then... but I usually use both syntax. Sometimes in the same query.
|
|
|
|
|
I use it almost weekly; as an example of what not to do
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
|
I used to... but not anymore.
|
|
|
|
|
Daily, yes. You just have to be very careful with how you write the queries and constantly inspect what Linq-to-SQL projects into actual SQL. Sometimes Linq is so clever that it project terrible and slow queries but in most cases you can fix it by "rewording" your Linq queries.
I believe Entity Framework has the same projection problem.
My plan is to live forever ... so far so good
|
|
|
|
|
Entity Framework Core for me. I like how it does migrations, and if done right, it can be portable across multiple database engines.
|
|
|
|
|
Never have, I dont mind writing proper code
|
|
|
|
|
Nope.
MS did suggest a while ago that it should not be used production wise, rather use EF or some such.
|
|
|
|
|
Nope. Since I write mainly in VB I find the Linq syntax to be very cumbersome and hard to use. When I write in C# I'm far more likely to use Linq simply because the lambda syntax is far easier to read and use. In neither case do I use Linq -> SQL
|
|
|
|
|
It is the recommended way for SharePoint 2010 CRUD according to "SharePoint 2010 Dev with VS2010" by E. Carter et al.
I use it and love having some of that back end taken care of (and i've really grown to like Linq). but as someone else said i use straight up SQL when the going gets tough.
|
|
|
|
|
Tried it for a project but quickly had to abandon it. Found it too rigid. If you try using against a many databases. When one database adds a field, it completely breaks querying the table.
Though I enjoyed learning about CROSS APPLY from examining it but discovered that it hits a cap where it performs better than anything else in a limited use environment, but once you pass a threshold it takes down systems.
|
|
|
|
|
Are Stilettos just arch enemies?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
If the shoe fits...
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Get to the point!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
They're at the height of fashion!
They call me different but the truth is they're all the same!
JaxCoder.com
|
|
|
|
|
Wasnt it John Bunyan who said that?
|
|
|
|
|
|
Would you call a pot smoking low life a High Heel?
They call me different but the truth is they're all the same!
JaxCoder.com
|
|
|
|
|
Only if his pot was laced with something else.
/ravi
|
|
|
|
|
C'mon, have you no sole?
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
