Started 5 days, 6 hours ago (2009-11-26 10:56:00)
by Abhishek sur
I think MySql will be better if the size of the data is very long. Reading the entire xml file into memory and then apply
LINQ will not be great compared to Database. In case of database you can select only the part you want. XML files are read totally into memory before searching.
Started 6 days ago (2009-11-25 16:36:00)
by MREcoolio
The way I used to do it w/ LINQ2SQL is to generate an interface on the table, for each table class in the datacontext. I would then manually go through each interface and convert it to a class. I'm not sure if someone has figured out how to automate this. After a year of so, I bought a commercial ORM from Mindscape called
Lightspeed, it supports linq and generates the DTOs for me =)
Started 6 days, 12 hours ago (2009-11-25 04:30:00)
by d@nish
IMO this [ ^ ] is a must visit for anyone starting with LINQ.
Started 1 week ago (2009-11-23 21:24:00)
by Eslam Afifi
Using the let clause [ ^ ] your query becomes var records = from record in document.Descendants( " Variable" ) let type = Support.GetType((string)record.Element( " type" )) select new Variable { Name = (string)record.
Element( " name" ), DataType = type, DefaultValue = Support. Convert ((...
Started 1 week, 6 days ago (2009-11-18 16:07:00)
by PunkIsNotDead
You only should get the
foreign key of tableb! according to your example... unless you've selected some data of tableb like result.tableb.fieldOfTableB
Started 2 weeks, 1 day ago (2009-11-15 18:11:00)
by Mark Nischalke
Tauseef A wrote: ut its not in the case of linq ? Yes, it is still the case with Linq. Your implementation and understanding is incorrect. Adding Linq to SQL or Entity Framework does not negate a properly implemented nLayer architecture. Your
presentation layer should only know about the entity objects, either via DTOs you create at the business layer or self contained Entity objects ...
Started 2 weeks, 4 days ago (2009-11-13 11:43:00)
by Abhishek sur
LINQ is
Language Integrated Query. Read this Basics of LINQ & Lamda Expressions [ ^ ] I hope you will get some concept from my article.
Started 2 weeks, 4 days ago (2009-11-13 03:30:00)
by Andreas X
You are not doing it wrong. Linq is generating a delete statement for each row in the table and matches the row to delete on all columns. This is why it takes a lot of time. the ExecuteCommand is the prefered way in this scenario