I have played with the LINQ to DataSet stuff, but to me
it didn't seem any more simple than doing regular SQL queries.
One of the claimed advantages is that you get compile-time checking of the
syntax of your linq query so you can know about syntax errors earlier in the
process. However, if I'm writing a sql statement I'm (probably :-) going to
test is as soon as I write it by running the program, so I'll know about
errors right away anyway -- so I'm with you, doesn't make sense to me.
Now linq to objects, that does make some sense, when I have a List<T> and I
want some subset of that list for an action linq is great -- especially when
the subset is more complicated than FindAll() can manage simply.
Walden H Leverich III
Tech Software &
BEC - IRBManager
(516) 627-3800 x3051
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
This is the .net use with the System i (SystemiDotNet) mailing list
To post a message email: SystemiDotNet@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.