System.Data.SQLite

Hi,

First I would like to say thank you for an excellent mapping. It has worked like a charm so far.

However, I'm planning to start a new project based on your library and now that MS soon will release LINQ I'm curious if I'm going to be able to use it for my project. So what is exactly is the planed time schedule for the LINQ support in SQLite. Will it for instance be ready when the SP1 for VS2005 is released?

Best Regards
    //Jan Persson

When LINQ, specifically the Entity Framework hist the next rev, I should be ready for it.  I haven't downloaded the latest October Orcas release yet - been too busy.  They will probably have a first beta early next year I'd imagine.  I should be able to release a corresponding provider and hit all the major betas and RC's until it RTM's.

I don't really expect the Entity Framework to RTM until late next year, though.

There are a lot of things missing from the current Entity Framework (inserts/updates through eSQL are the most glaring omission).  Knowing that these will get cooked in, and there may be some tweaks to eSQL and the mapping schemas, I personally am holding off writing any serious code with it just yet.

I am however, committed to supporting it in the SQLite provider as things develop.

Robert

 

Thank you. It's much clearer now. My main problem understanding the release schedule was that I thought c# 3.0 was a part of .NET 3.0. That does not seem to be the case and it has been very confusing up until now.

Regards
    //Jan

I agree its all very confusing.  The way I understand it, LINQ and the Entity Framework will be part of Orcas, and won't ship until sometime in mid to late 2007.  Here's a brief "off the top of my head" list of missing features of the current LINQ CTP:

• Insert/Update/Delete support in eSQL
• Entity Metadata, for providers to describe their support functionality to the mapping provider
• Stored proc support (not really important for SQLite, but missing nontheless)
• Metadata for informing the mapping layer what functions and aggregate functions the provider supports (avg, min, max, regexp, etc).
• DDL to have a standardized method of adding/altering/deleting tables/indexes/columns/etc.  This may or may not happen at all, and may end up in a future version of LINQ if it does happen.

Hi,

I'm wondering what the status of the SQLite vNext provider is now that the Orcas March CPT is out.  Will the SQLite prover support Linq for SQL?

~ Paul
PS I think the work you've done on this is amazing.  Thank You!

Yes, absolutely 100% there'll be a LINQ provider for SQLite.  I'm just getting hammered with work right now and haven't had time in the last few weeks to do any updates.  I'm also taking the family on vacation next week for 3 weeks, so I'm trying to wrap up all my projects before I leave.

Things will calm down in April and I'll be able to get back on track.

Robert

 

Any news ? I'm running Orcas Beta 1 and would love to start using it.

Good luck!

 I finally understand the mail I got from you some time ago, saying LINQ wasn't released yet.

What you actually meant was that the Entity Framework wasn't released yet,
I was unaware you'd be using the entity framework to implement LINQ to SQLite.

LINQ itself had already been released at the time we communicated by mail.
Why exactly will you be using the entity framework?

 

System.Data.Linq  AKA linq to SQL is Microsoft SqlServer only.  Implementing a similar library would be pretty trivial since the library was designed with database independence in mind.  You'd only have to really implement a new DBContext class.  However what you wouldnt get is all the designer support.  The Visual Studio LinqToSql designer actually puts out quite a bit of code in your .designer.cs file.  If we were to implement such a library end users would have to write all that code themselves where as Entity Framework gets it for free.  More over EntityFramework is what microsoft is billing as "The Future".  It supports many more features and divierse database interaction schemes than LinqToSql.