Linq to Sql providers

I have two questions regarding Linq to Sql providers:
1. Are there any other besides MS SQL Server available?
2. How to program custom Linq to Sql provider? (Obviously I expect only some
guidelines and "getting started" type of advice.

Thank you in advance,

Roger

Frans
Mon Jun 30 02:17:07 CDT 2008

dsaf wrote:
> I have two questions regarding Linq to Sql providers:
> 1. Are there any other besides MS SQL Server available?

Linq to Sql is for MS SQL Server. If you want to use Linq with another
type of database you need something else than Linq to Sql.

> 2. How to program custom Linq to Sql provider? (Obviously I expect only some
> guidelines and "getting started" type of advice.

Linq to Sql doesn't support custom providers as a necessary interface
is internal. You therefore can't write support for other databases. It
also would have been very difficult to do so, as writing a Linq provider
isn't easy.

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

Miha
Mon Jun 30 06:04:29 CDT 2008

In addition to Frans' comment.
If you are looking for a best ORM out there then check out Frans'
LLBLGenPro - you won't regret it.
If you are just looking to a free LINQ to SQL alternative that supports
multiple databases (plus other improvements) then take a look at forthcoming
Entity Framework.
There is also a plethora of both free and commercial ORM products out
there...

--
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

"dsaf" <dsf> wrote in message news:uc1hMol2IHA.5832@TK2MSFTNGP02.phx.gbl...
>I have two questions regarding Linq to Sql providers:
> 1. Are there any other besides MS SQL Server available?
> 2. How to program custom Linq to Sql provider? (Obviously I expect only
> some guidelines and "getting started" type of advice.
>
> Thank you in advance,
>
> Roger
>

Misbah
Mon Jun 30 16:05:56 CDT 2008

From Charlie Calvert's Blog
http://blogs.msdn.com/charlie/archive/2008/02/28/link-to-everything-a-list-of-linq-providers.aspx

DbLinq Project: Linq Provider for MySql, Oracle and PostgreSQL
http://code2code.net/DB_Linq/


--
Misbah Arefin
https://mcp.support.microsoft.com/profile/MISBAH.AREFIN
http://dotnethitman.spaces.live.com
http://www.linkedin.com/in/misbaharefin




"dsaf" <dsf> wrote in message news:uc1hMol2IHA.5832@TK2MSFTNGP02.phx.gbl...
> I have two questions regarding Linq to Sql providers:
> 1. Are there any other besides MS SQL Server available?
> 2. How to program custom Linq to Sql provider? (Obviously I expect only
> some guidelines and "getting started" type of advice.
>
> Thank you in advance,
>
> Roger
>
>

dsaf
Mon Jun 30 18:01:13 CDT 2008


>> I have two questions regarding Linq to Sql providers:
>> 1. Are there any other besides MS SQL Server available?
>
> Linq to Sql is for MS SQL Server.

Why then MS doesn't say so, as in "Linq to MSSQL"?

>If you want to use Linq with another type of database you need something
>else than Linq to Sql.

It seems I will have to. I would prefer solution that comes with .Net but MS
is just not making it possible. Don't really understand this decision, they
decided to officially provide an ORM solution (shipped with framework 3.5)
but then they decide to lock it in.

>> 2. How to program custom Linq to Sql provider? (Obviously I expect only
>> some guidelines and "getting started" type of advice.
>
> Linq to Sql doesn't support custom providers as a necessary interface is
> internal. You therefore can't write support for other databases. It also
> would have been very difficult to do so, as writing a Linq provider isn't
> easy.

But is far from impossible...

FB, I thank you for your help

Best,

Roger

> FB

dsaf
Mon Jun 30 18:04:17 CDT 2008

Thank you Mishbah.

Alas, as I understood from previous replies, I will not be able to plug
these providers into Linq to Sql, since this is not supported. It seems this
could have been a rather simple solution...


"Misbah Arefin" <MisbahArefin@discussions.microsoft.com> wrote in message
news:17504A71-47E0-48A7-97E8-D5F9228E40A3@microsoft.com...
> From Charlie Calvert's Blog
> http://blogs.msdn.com/charlie/archive/2008/02/28/link-to-everything-a-list-of-linq-providers.aspx
>
> DbLinq Project: Linq Provider for MySql, Oracle and PostgreSQL
> http://code2code.net/DB_Linq/
>
>
> --
> Misbah Arefin
> https://mcp.support.microsoft.com/profile/MISBAH.AREFIN
> http://dotnethitman.spaces.live.com
> http://www.linkedin.com/in/misbaharefin
>
>
>
>
> "dsaf" <dsf> wrote in message
> news:uc1hMol2IHA.5832@TK2MSFTNGP02.phx.gbl...
>> I have two questions regarding Linq to Sql providers:
>> 1. Are there any other besides MS SQL Server available?
>> 2. How to program custom Linq to Sql provider? (Obviously I expect only
>> some guidelines and "getting started" type of advice.
>>
>> Thank you in advance,
>>
>> Roger
>>
>>

Frans
Tue Jul 01 03:06:56 CDT 2008

dsaf wrote:
>>> I have two questions regarding Linq to Sql providers:
>>> 1. Are there any other besides MS SQL Server available?
>> Linq to Sql is for MS SQL Server.
>
> Why then MS doesn't say so, as in "Linq to MSSQL"?

that's something for MS to answer ;)

>> If you want to use Linq with another type of database you need something
>> else than Linq to Sql.
>
> It seems I will have to. I would prefer solution that comes with .Net but MS
> is just not making it possible. Don't really understand this decision, they
> decided to officially provide an ORM solution (shipped with framework 3.5)
> but then they decide to lock it in.

If you want an O/R mapper with full linq support, check LLBLGen Pro:
http://www.llblgen.com . I'm the lead developer of LLBLGen Pro.

>>> 2. How to program custom Linq to Sql provider? (Obviously I expect only
>>> some guidelines and "getting started" type of advice.
>> Linq to Sql doesn't support custom providers as a necessary interface is
>> internal. You therefore can't write support for other databases. It also
>> would have been very difficult to do so, as writing a Linq provider isn't
>> easy.
>
> But is far from impossible...

True, it costed me 10 months full time work :)

See my blog (see sig) for the articles I wrote about writing a Linq
provider.

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

Cor
Tue Jul 01 04:59:44 CDT 2008

Frans,

Advertising time is over again. Let others do that for you in newsgroups.

Miha and I have not any problem with that.

:-)

Cor

"Frans Bouma [C# MVP]" <perseus.usenetNOSPAM@xs4all.nl> schreef in bericht
news:%23SRpxF12IHA.5060@TK2MSFTNGP02.phx.gbl...
> dsaf wrote:
>>>> I have two questions regarding Linq to Sql providers:
>>>> 1. Are there any other besides MS SQL Server available?
>>> Linq to Sql is for MS SQL Server.
>>
>> Why then MS doesn't say so, as in "Linq to MSSQL"?
>
> that's something for MS to answer ;)
>
>>> If you want to use Linq with another type of database you need something
>>> else than Linq to Sql.
>>
>> It seems I will have to. I would prefer solution that comes with .Net but
>> MS is just not making it possible. Don't really understand this decision,
>> they decided to officially provide an ORM solution (shipped with
>> framework 3.5) but then they decide to lock it in.
>
> If you want an O/R mapper with full linq support, check LLBLGen Pro:
> http://www.llblgen.com . I'm the lead developer of LLBLGen Pro.
>
>>>> 2. How to program custom Linq to Sql provider? (Obviously I expect only
>>>> some guidelines and "getting started" type of advice.
>>> Linq to Sql doesn't support custom providers as a necessary interface is
>>> internal. You therefore can't write support for other databases. It also
>>> would have been very difficult to do so, as writing a Linq provider
>>> isn't easy.
>>
>> But is far from impossible...
>
> True, it costed me 10 months full time work :)
>
> See my blog (see sig) for the articles I wrote about writing a Linq
> provider.
>
> FB
>
> --
> ------------------------------------------------------------------------
> Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
> LLBLGen Pro website: http://www.llblgen.com
> My .NET blog: http://weblogs.asp.net/fbouma
> Microsoft MVP (C#)
> ------------------------------------------------------------------------

Frans
Wed Jul 02 03:18:28 CDT 2008

Cor Ligthert [MVP] wrote:
> Frans,
>
> Advertising time is over again. Let others do that for you in newsgroups.
>
> Miha and I have not any problem with that.

I didn't know I needed your permission

FB

>
> :-)
>
> Cor
>
> "Frans Bouma [C# MVP]" <perseus.usenetNOSPAM@xs4all.nl> schreef in bericht
> news:%23SRpxF12IHA.5060@TK2MSFTNGP02.phx.gbl...
>> dsaf wrote:
>>>>> I have two questions regarding Linq to Sql providers:
>>>>> 1. Are there any other besides MS SQL Server available?
>>>> Linq to Sql is for MS SQL Server.
>>> Why then MS doesn't say so, as in "Linq to MSSQL"?
>> that's something for MS to answer ;)
>>
>>>> If you want to use Linq with another type of database you need something
>>>> else than Linq to Sql.
>>> It seems I will have to. I would prefer solution that comes with .Net but
>>> MS is just not making it possible. Don't really understand this decision,
>>> they decided to officially provide an ORM solution (shipped with
>>> framework 3.5) but then they decide to lock it in.
>> If you want an O/R mapper with full linq support, check LLBLGen Pro:
>> http://www.llblgen.com . I'm the lead developer of LLBLGen Pro.
>>
>>>>> 2. How to program custom Linq to Sql provider? (Obviously I expect only
>>>>> some guidelines and "getting started" type of advice.
>>>> Linq to Sql doesn't support custom providers as a necessary interface is
>>>> internal. You therefore can't write support for other databases. It also
>>>> would have been very difficult to do so, as writing a Linq provider
>>>> isn't easy.
>>> But is far from impossible...
>> True, it costed me 10 months full time work :)
>>
>> See my blog (see sig) for the articles I wrote about writing a Linq
>> provider.


--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

Cor
Wed Jul 02 05:43:10 CDT 2008

>
> I didn't know I needed your permission
>
Not mine, I tried to warn you that others maybe would do that.

:-)

Cor