System.Data.SQLite

I'll periodically update this as time goes by.

Here's a tentative roadmap for some of the complex features I'd like to implement and when I expect to have them working.  If you have additional complex requirements for the provider please feel free to request it.

Q3 2008

• Allow the automatic loading and registration of external assemblies through the use of a sqlite_assemblies table.  The provider will enumerate this table if found in a SQLite database, load up the referenced assemblies and hook up all their custom functions automatically.
• Add the necessary design-time components to the VS designer to allow you to manage the sqlite_assemblies table.
• It may be possible to actually embed the assembly into this table entirely.  Compact Framework will require special consideration and coding.

Q4 2008

• Implement virtual tables.  This will be used in conjunction with the sqlite_assemblies table to automatically load the modules required by the virtual tables in the database.

Q1 2009

• Implement SQLite's VFS (virtual file system).  This will allow the provider to work on Isolated Storage and C# Streams.  There will be a performance penalty, but the feature is cool enough to warrant it.

Q? 2009

• Implement C#/VB stored procs.  This will require revamping a lot of internal implementations of classes like SQLiteStatement and SQLiteDataReader, as well as implementing the mechanism itself.
• This mechanism will also use the sqlite_assemblies table implementation.

Robert

 May I suggest switching the vfs and virtual table implementation items?  They both pose similar technical challenges in regards to declaration, pinning, naming etc.  However the vfs system has fewer and smaller objects, more in-depth documentation as well as 3 relatively simple and well-documented example implementations.

In the road map you mention that the implementation of the VFS will allow the provider to use C# streams.  Would it be possible to use a stream that supports compression?

The idea is that you can attach any Stream object, or any object that implements the Stream base class.  It would be up to you to implement a compressible stream.  So the answer is yes, but I do not intend to implement that myself.

 I believe it would be possible.  Implementing a read-only decompressing vfs would be pretty trivial.  However, a vfs supporting read-write and compression would be significantly more complex to implement than a simple stream vfs.  It would have to work much more like an encrypting vfs, compressing and decompressing specific chunks of the stream.