System.Data.SQLite

If these three methods would work with SQLite, it would be very useful for unit testing, as it is the only database engine that supports pure memory-backed databases (via "Data Source=:memory:"), making it easy to allow unit tests for the DB mapping layer to run in parallel to each other.

anonymous added on 2012-01-26 09:29:47 UTC:
Here's a chunk of example code for EF 4.2 that reproduces the errors:

public class Post {
	public string Title { get; set; }
}
public class BlogContext : DbContext {
	public BlogContext() : base(nameOrConnectionString: "BlogConnection") { }
	public DbSet<Post> Posts { get; set; }
}
class Program {
	static void Main(string[] args) {
		Database.SetInitializer<BlogContext>(
			new CreateDatabaseIfNotExists<BlogContext>()
		);
		using(var context = new BlogContext()) {
			context.Posts.Add(new Post() { Title = "Test" });
			context.SaveChanges();
		}
	}
}

Of course, the appropriate App.config needs to be in place:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
	<system.data>
		<DbProviderFactories>
			<remove invariant="System.Data.SQLite" />
			<add
				name="SQLite Data Provider"
				invariant="System.Data.SQLite"
				description="Data Provider for SQLite"
				type="System.Data.SQLite.SQLiteFactory, System.Data.SQLite"
			/>
		</DbProviderFactories>
	</system.data>
	<connectionStrings>
		<add
			name="BlogConnection"
			providerName="System.Data.SQLite"
			connectionString="Data Source=:memory:"
		/>
	</connectionStrings>
</configuration>

Is there any news about this issue? I plan to use SQLite in a EF4 "Code First" project, but due to this missing feature I can't do so.

During my investigation I found following background:

1) ObjectContext.CreateDatabase is used to create a new database (http://msdn.microsoft.com/en-us/library/system.data.objects.objectcontext.createdatabasescript.aspx). It is stated in docs, that: "most work is delegated to:"

2) DbProviderServices.CreateDatabase Method (http://msdn.microsoft.com/en-us/library/system.data.common.dbproviderservices.createdatabase.aspx)

3) But there is already a SQLiteProviderServices class that derives from DbProviderServices (http://system.data.sqlite.org/index.html/artifact/d69370467b6ce499f16026c7b2e54332990be6aa)

So what else is missing? How much effort it would take to implement the missing features?

I really would like to have a version that works with "Code First" EF feature!

Thank you very much!

Found some more information that may be helpful

http://archive.msdn.microsoft.com/EFSampleProvider, the source code can be downloaded

The Entity Framework 6 is now supported.