System.Data.SQLite

Perhaps read Robert's article detailing fast bulk insertion: http://sqlite.phxsoftware.com/forums/t/134.aspx

A quick search of the forum reveals the answer (several times). Here is one such answer: http://sqlite.phxsoftware.com/forums/p/1978/8348.aspx#8348

Have you verified that your two invocations of date() are returning meaningful values? For instance, if you run the command-line 'sqlite3' program and invoke "select date('somevalue');", does it return what you expect?

Since your question is generic, rather than specific to the .NET System.Data.SQLite wrapper, you may get a response more quickly by asking on the general 'sqlite-users' mailing list: http://www.sqlite.org/support.html

Hi Héctor. Your question is general to SQLite, rather than specific to the managed wrapper System.Data.SQLite. Therefore, you probably can get a better and faster response from the 'sqlite-users' mailing list: http://www.sqlite.org/support.html

Please note that the sample code kindly provided by Juve86's is pure C++, and thus does not take advantage of managed System.Data.SQLite at all, in which case the raw http://www.sqlite.org/ could be used instead. If you indeed want to use managed C++, then you need only make some minor adjustments to your code. Specifically, objects returned ...

Perhaps http://www.sqlite.org/lang_expr.html#like or http://www.sqlite.org/pragma.html#pragma_case_sensitive_like is relevant to your case.

Indices to substr() are 1-based, so your invocation substr(Date, 0, 2) is bogus. It should be substr(Date, 1, 2). A quick test with the sqlite command-line program confirms this: sqlite> select substr('21/6/2010', 1, 2); 21 sqlite> select substr('21/6/2010', 0, 2); 2

To my knowledge, this is not possible.

You are not being clear. If you do not want to constraint what is returned, then omitting the WHERE clause is the correct approach. If you have some other intention in mind, then you have to explain it in more detail.