Database query language
-
Hi there...i am recently going to start work on databases in which i will have to insert,delete,log,update,match entries.. the language in general i will use c#...my question is..what query lanquage is the easier and convinient way to do these? Ado.net or LINq....which one i should learn first ?? and which one is easy?...please guide!
-
Hi there...i am recently going to start work on databases in which i will have to insert,delete,log,update,match entries.. the language in general i will use c#...my question is..what query lanquage is the easier and convinient way to do these? Ado.net or LINq....which one i should learn first ?? and which one is easy?...please guide!
I'd learn them in this order: SQL: Can use on pretty much any modern DB system. ADO.NET: Relies on SQL at the bottom so a working knowledge if that is important LINQ: Although it as abstracted away, it uses ADO at the bottom and has many similarities to SQL, and sometimes/often you need to write raw SQL. But I'd use them in the following order of preference: LINQ + SQL --> ADO + SQL. Personally I rarely feel the need for plain ADO any more (DataSets = X|), but I do find it useful to know how they all work.
Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^] -
Hi there...i am recently going to start work on databases in which i will have to insert,delete,log,update,match entries.. the language in general i will use c#...my question is..what query lanquage is the easier and convinient way to do these? Ado.net or LINq....which one i should learn first ?? and which one is easy?...please guide!
Linq will only work with Microsoft technologies -- pretty much just .net and SQL Server -- so it may stunt your growth. SQL is a more general solution and once you know it you can use it with a number of database systems and access methods, e.g. ADO.net, ODBC, embedded. As to ADO.net, I recommend encapsulating it into a framework that you can easily understand and use. Of course, you'd be even better off mastering everything. :-D
-
Linq will only work with Microsoft technologies -- pretty much just .net and SQL Server -- so it may stunt your growth. SQL is a more general solution and once you know it you can use it with a number of database systems and access methods, e.g. ADO.net, ODBC, embedded. As to ADO.net, I recommend encapsulating it into a framework that you can easily understand and use. Of course, you'd be even better off mastering everything. :-D
-
yeah i know it has limitations..infact i was asking in short term period working with sql server and c#...so only in that context would first learning Linq be ok?..at the moment just have to work on a simple database.
I wouldn't use it for a enterprise application, but that's just me.
-
Linq will only work with Microsoft technologies -- pretty much just .net and SQL Server -- so it may stunt your growth. SQL is a more general solution and once you know it you can use it with a number of database systems and access methods, e.g. ADO.net, ODBC, embedded. As to ADO.net, I recommend encapsulating it into a framework that you can easily understand and use. Of course, you'd be even better off mastering everything. :-D
PIEBALDconsult wrote:
Linq will only work with Microsoft technologies -- pretty much just .net and SQL Server
Not really, LINQ has three main parts: 1: LINQ to SQL 2: LINQ to Objects 3: LINQ to XML (yes, there are more 'flavors') both LINQ to Objects and LINQ to XML can still be used and quite powerful while not connecting to SQL-Server. (it does more or less imply that you stay in .Net though)
V.
-
Hi there...i am recently going to start work on databases in which i will have to insert,delete,log,update,match entries.. the language in general i will use c#...my question is..what query lanquage is the easier and convinient way to do these? Ado.net or LINq....which one i should learn first ?? and which one is easy?...please guide!
As already said, basics of SQL should be learned first. But when you start to go deeper, have a look at these excellent books: Amazon's Complete Selection of Joe Celko Books[^]
The need to optimize rises from a bad design.My articles[^]