Why the name "DLinq"?

Question

Any reason for why it's called "DLinq"?  It seems that calling it "RLinq", with the R for Relational, or "SLinq", with the S for SQL, would make more sense.

Answer 1

What if the Database isn't SQL, or Relational?

Such databases do exist...

Answer 2

Well, the description for this DLinq forum does state "Ask questions about DLinq, the LINQ-enabled API for relational data." (emphasis added).

Answer 3

It stands for "Database Language Integrated Query"
XLINQ stands for "XML Language Integrated Query"

correct me if I am wrong

Answer 4

The previous post describes it quite well.

Thanks.
Dinesh Kulkarni
Program Manager - DLinq
http://blogs.msdn.com/Dinesh.Kulkarni/

Answer 5

What I was getting at, myself, was that the name, "DLinq" (though not necessarily "XLinq"), follows the principle of "Don't tie yourself to any particular technology, for tomorrow it may die."

Answer 6

Good point. However, the DLinq component itself does translate to SQL and relies on relational features in the current incarnation. What you describe is indeed the goal of C# 3.0 features. Sequence operators, DLinq, XLinq are specific applications of a general set of language features.

Thanks.

Dinesh Kulkarni
http://blogs.msdn.com/Dinesh.Kulkarni/

Answer 7

This is true.. However, as you allude, it need not remain so.

I think it wouldn't take much to have a pluggable DataContext provider which would contain the logic for determining what to send to the server.  I'm guessing the translation logic is in DataContext, and not Table<>?

Actually, I think it'd be great to just send the expression tree to the server, but that's just me. ;)

Speaking of which, is there anywhere a good (read:  don't have to write it myself) means to translate an Expression tree into a CodeDOM, or some other means of compilation?